Resources running on a Pacemaker remote node stay in stopped state when a remote node is fenced with pcs stonith fence
Issue
- After I fence a Pacemaker remote node manually with
pcs stonith fence
orstonith_admin
, any resource that was running on it stays in Stopped state until the remote node rejoins the cluster.
BEFORE:
# pcs status
...
Node List:
* Online: [ node1 node2 ]
* RemoteOnline: [ node3-rem node4-rem ]
Full List of Resources:
* xvm (stonith:fence_xvm): Started node1
* node3-rem (ocf:pacemaker:remote): Started node1
* node4-rem (ocf:pacemaker:remote): Started node2
* dummy1 (ocf:heartbeat:Dummy): Started node3-rem
AFTER:
# pcs status
...
Node List:
* Online: [ node1 node2 ]
* RemoteOnline: [ node4-rem ]
* RemoteOFFLINE: [ node3-rem ]
Full List of Resources:
* xvm (stonith:fence_xvm): Started node1
* node3-rem (ocf:pacemaker:remote): FAILED node1
* node4-rem (ocf:pacemaker:remote): Started node2
* dummy1 (ocf:heartbeat:Dummy): Stopped
Environment
- Red Hat Enterprise Linux 8 (with the High Availability Add-on)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.