Node does not reboot when "self_fence=on" and "force_unmount=on" are set and a submount causes an fs resource to fail in RHEL 6
Issue
- If an
fs
(filesystem) resource fails to stop due to an active submount,self_fence
is not honored (the node doesn't reboot). - The
self_fence=on
logic doesn't get triggered in some situations whenforce_unmount
option is enabled.
Environment
- Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
resource-agents
releases prior to3.9.2-40.el6
- One or more filesystem-based resources (
fs
,clusterfs
,netfs
, etc) in/etc/cluster/cluster.conf
.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.