Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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 the "pcs stonith confirm" command in the man page and built-in help has been clarified to avoid confusion about what the command actually does and should be used for.
Description of problem:
Following man page about "stonith confirm" is unclear or wrong.
man 8 pcs
Confirm <node> [--force]
Confirm that the host specified is currently down. This command
should ONLY be used when the node specified has already been
confirmed to be powered off and to have no access to shared
resources.
Version-Release number of selected component (if applicable):
pcs-0.9.158-6.el7.x86_64.rpm
Detail:
"pcs stonith fence <node>" fence the node immidiately.
"pcs stonith confirm <node>" fence the node _after_ the user's confirmation.
That's the diference between these 2 commands.
First of all, the command option "confirm" make us confusing.
It should be "confirm_and_fence".
But I don't think we can change the command option,
so I propose to change the online manual, instead.
confirm <node> [--force]
Issue fence to target <node> after user's confirmation.
Adding --force override the confirmation.
This command will get the target node to be fenced.
This command should ONLY be used when the node specified has
already been confirmed to be powered off and to have
no access to shared resources.
Additional information:
Following document page also need to be fixed.
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/High_Availability_Add-On_Reference/index.html
You can confirm whether a specified node is currently powered off with the following command.
Note
If the node you specify is still running the cluster software or services normally controlled by the cluster, data corruption/cluster failure will occur.
pcs stonith confirm node
Related BZ
https://bugzilla.redhat.com/show_bug.cgi?id=1489674
Same subject on RHEL6.
pcs runs "stonith_admin -C <node>". Ken, can you take a look at what it actually does in respect to what has been described in comment 0? There is a bit more info in bz1489674. Thanks!
"stonith_admin -C" and "pcs stonith confirm" do *NOT* fence the node. They allow the administrator to tell the cluster that a node is safely off, so that the cluster is not blocked after a failed fencing request. The typical use case is:
* The cluster needs to fence a node, for any reason (network loss, failed resource stop, etc.).
* Either no stonith devices are capable of fencing the node, or all capable devices fail.
* The cluster refuses to recover the target node's resources on another node because fencing did not succeed.
* The administrator manually ensures that the target node is powered down, then runs "pcs stonith confirm" to tell the cluster it is safe to proceed. The cluster will now recover the resources as if stonith succeeded.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:0866
Description of problem: Following man page about "stonith confirm" is unclear or wrong. man 8 pcs Confirm <node> [--force] Confirm that the host specified is currently down. This command should ONLY be used when the node specified has already been confirmed to be powered off and to have no access to shared resources. Version-Release number of selected component (if applicable): pcs-0.9.158-6.el7.x86_64.rpm Detail: "pcs stonith fence <node>" fence the node immidiately. "pcs stonith confirm <node>" fence the node _after_ the user's confirmation. That's the diference between these 2 commands. First of all, the command option "confirm" make us confusing. It should be "confirm_and_fence". But I don't think we can change the command option, so I propose to change the online manual, instead. confirm <node> [--force] Issue fence to target <node> after user's confirmation. Adding --force override the confirmation. This command will get the target node to be fenced. This command should ONLY be used when the node specified has already been confirmed to be powered off and to have no access to shared resources. Additional information: Following document page also need to be fixed. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/High_Availability_Add-On_Reference/index.html You can confirm whether a specified node is currently powered off with the following command. Note If the node you specify is still running the cluster software or services normally controlled by the cluster, data corruption/cluster failure will occur. pcs stonith confirm node Related BZ https://bugzilla.redhat.com/show_bug.cgi?id=1489674 Same subject on RHEL6.