RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.