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.
A fenced node in an ‘sbd’ setup now shuts down reliably
Previously, when a node received an ‘off’ via the poison pill mechanism used by ‘sbd’ on a shared disk, the node would be likely to reboot instead of powering off. With this fix, receiving an ‘off’ will power off the node. Receiving a ‘reset’ will reboot the node. If the node is not able to perform the software-driven reboot or power off properly, the watchdog is going to trigger and the action performed is what the watchdog device is configured to. A fenced node in an ‘sbd’ setup now shuts down reliably if the watchdog device is configured to power off the node, and fencing is requesting ‘off’ via the poison pill mechanism on a shared disk.
DescriptionKlaus Wenninger
2017-07-07 12:43:31 UTC
Description of problem:
In an sbd-setup where the watchdog is set to poweroff the node and fencing-action off is issued for a node via a shared-disk.
Version-Release number of selected component (if applicable):
sbd-1.3.0-3.el7
How reproducible:
100%
Steps to Reproduce:
1. setup virtual cluster using qemu-kvm
2. configure sbd using a shared disk
3. pcs stonith update {sbd-fencing-resource} method=onoff
4. pcs property set stonith-action=poweroff
3. pcs stonith fence {target-node}
Actual results:
fenced node reboots instead of shutting down
Expected results:
fenced node should shut down
Additional info:
mentioned reproduction via qemu-kvm as it is basically a race that might not be 100% reproducible on other platforms
Steven:
Guess that mixes up things now.
It really has to be distinguished between watchdog-configuration, what fencing is configured and what subsequently is signalled via poison-pill to the other side.
Guess you wanted it to be nearer to the test that lead to discovering the issue.
My approach was rather to describe which part of that went wrong and fixed now - so that other use-cases that trigger the same thing would be easier to detect/understand. I'll think over it under that light again tomorrow.
Steven:
Tried to modify the 'Doc Text' in the direction of your suggestion starting with the explicit use-case that is now working and describing a little bit what has been fixed under the hood in the paragraph following.
One semantic question arises: A watchdog is triggered (kicked) to stay calm and it triggers an action when it runs off - at least in my understanding of the words. Maybe 'trigger' should thus rather not be used in favour of 'kick' for the one thing and something like 'run off' for the other. But I'm not sure and we should probably do it consistently.
Comment 17Steven J. Levine
2018-03-14 18:59:44 UTC
Klaus:
The first line of the description in the doc text becomes a title for the entry, and there is a character limit. So I had to shorten the sentence to its first phrase (what the user will see at a quick glance) but moved the whole original sentence to the end of the description, since that's what this leads to.
I think that for the purposes of this release note your phrasing is fine as it. It's really just to let somebody know what the problem was and the nature of the fix, and I think this is clear enough.
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:0924
Description of problem: In an sbd-setup where the watchdog is set to poweroff the node and fencing-action off is issued for a node via a shared-disk. Version-Release number of selected component (if applicable): sbd-1.3.0-3.el7 How reproducible: 100% Steps to Reproduce: 1. setup virtual cluster using qemu-kvm 2. configure sbd using a shared disk 3. pcs stonith update {sbd-fencing-resource} method=onoff 4. pcs property set stonith-action=poweroff 3. pcs stonith fence {target-node} Actual results: fenced node reboots instead of shutting down Expected results: fenced node should shut down Additional info: mentioned reproduction via qemu-kvm as it is basically a race that might not be 100% reproducible on other platforms