Red Hat Bugzilla – Bug 996576
Unfence at cluster startup with fence_scsi
Last modified: 2014-06-18 00:26:56 EDT
Description of problem: Pure pacemaker + fence_scsi does not provide complete fencing solution. The node needs to register with the device on which it's supposed to write prior to any write action. Until now this was done with cman + <unfence> mechanics which triggered fence_node -U at startup. Currently with pure pacemaker+corosync combo there is no trick to fire the same operation and get the node registered. Please provide a way to do such an action and sucessfully register with the device. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. setup a cluster with fence_scsi and compliant shared disk 2. startup the cluster 3. verify keys on the devices (sg_persist) Actual results: no keys present Expected results: keys present as in cman Additional info:
I should have a functioning patch later today. We'll also need to clone this for RHEL6.5 since 'fence_node -U' is a no-op when cluster.conf only references pcmk_fence. In any case, stonithd wouldn't be running to allow it to succeed. The same patch will address the issue in both versions.
A related patch has been committed upstream: https://github.com/beekhof/pacemaker/commit/8af0d0c with subject: Feature: Fencing: Support agents that need the host to be unfenced at startup Further details (if any):
This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request.