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.
Bug 996576 - Unfence at cluster startup with fence_scsi
Summary: Unfence at cluster startup with fence_scsi
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pacemaker
Version: 7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Andrew Beekhof
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On: 1009067 1009069
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-13 13:08 UTC by Jaroslav Kortus
Modified: 2014-06-18 04:26 UTC (History)
2 users (show)

Fixed In Version: pacemaker-1.1.10-16.el7
Doc Type: Bug Fix
Doc Text:
Cause: Fencing is configured in Pacemaker not cman Consequence: The call to fence_node -U in the cman init script is a no-op Fix: Support the concept of automated unfencing in pacemaker Result: Messages such as these should be visible in the log files during startup: stonith-ng[7472]: notice: cib_device_update: Unfencing ourselves with fence_scsi (Fabric) ... stonith-ng[7472]: notice: log_operation: Operation 'on' [7485] (call -1 from stonith-ng) for host 'pcmk-5' with device 'Fabric' returned: 0
Clone Of:
: 996850 (view as bug list)
Environment:
Last Closed: 2014-06-13 12:02:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Kortus 2013-08-13 13:08:01 UTC
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:

Comment 2 Andrew Beekhof 2013-08-14 00:45:35 UTC
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.

Comment 3 Andrew Beekhof 2013-08-14 07:01:02 UTC
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):

Comment 8 Ludek Smid 2014-06-13 12:02:56 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.