A fencing event occurred on a RHEL 6 `pacemaker` cluster that had `stonith-enabled` set to `false`?

Issue

• A fencing event occurred on a RHEL 6 pacemaker cluster that had stonith-enabled set to false:

Mar  7 10:06:42 node2 corosync[1610]:   [TOTEM ] A processor failed, forming new configuration.
Mar  7 10:06:44 node2 kernel: dlm: closing connection to node 1
Mar  7 10:06:44 node2 corosync[1610]:   [QUORUM] Members[1]: 2
Mar  7 10:06:44 node2 corosync[1610]:   [TOTEM ] A processor joined or left the membership and a new membership was formed.
Mar  7 10:06:44 node2 corosync[1610]:   [CPG   ] chosen downlist: sender r(0) ip(192.168.122.22) ; members(old:2 left:1)
Mar  7 10:06:44 node2 corosync[1610]:   [MAIN  ] Completed service synchronization, ready to provide service.
Mar  7 10:06:44 node2 crmd[1852]:  warning: match_down_event: No match for shutdown action on NODE1
Mar  7 10:06:44 node2 crmd[1852]:   notice: peer_update_callback: Stonith/shutdown of NODE1 not matched
Mar  7 10:06:44 node2 crmd[1852]:   notice: crm_update_peer_state: cman_event_callback: Node NODE1[1] - state is now lost (was member)
Mar  7 10:06:44 node2 crmd[1852]:  warning: match_down_event: No match for shutdown action on NODE1
Mar  7 10:06:44 node2 crmd[1852]:   notice: peer_update_callback: Stonith/shutdown of NODE1 not matched
Mar  7 10:06:44 node2 crmd[1852]:   notice: do_state_transition: State transition S_IDLE -> S_INTEGRATION [ input=I_NODE_JOIN cause=C_FSA_INTERNAL origin=check_join_state ]
Mar  7 10:06:44 node2 attrd[1850]:   notice: attrd_local_callback: Sending full refresh (origin=crmd)
Mar  7 10:06:44 node2 attrd[1850]:   notice: attrd_trigger_update: Sending flush op to all hosts for: readable (1)
Mar  7 10:06:44 node2 fenced[1678]: fencing node NODE1
[....]
Mar  7 10:06:44 node2 fenced[1678]: fence NODE1 dev 0.0 agent none result: error no method
Mar  7 10:06:44 node2 fenced[1678]: fence NODE1 failed

 stonith-enabled: false