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.
DescriptionKlaus Wenninger
2019-06-07 12:41:34 UTC
+++ This bug was initially created as a clone of Bug #1718296 +++
Description of problem:
When on a node that was put into maintenance-mode pacemaker is shut down all resources keep active.
That being detected by sbd when the pacemaker-connection goes away makes sbd
think the shutdown was ungracefully and thus it expects pacemaker to reconnect
immediately (watchdog-timeout).
Version-Release number of selected component (if applicable):
sbd-1.4.0-8.el8
How reproducible:
100%
Steps to Reproduce:
1. Setup cluster using sbd
2. Start cluster and wait till some resources are started on the node you want
to trigger the missbehaviour on
3. Bring the node into maintenance-mode using
'pcs node maintenance {your-test-node}'
4. Issue 'systemctl stop pacemaker' on {your-test-node}
Actual results:
Node is rebooted by sbd
Expected results:
Sbd should detect that the pacemaker-shutdown is still graceful and not trigger
a reboot.
Additional info:
The correction would be needed e.g. in an pacemaker-upgrade-scenario where the node is first set to maintenance. Then pacemaker is shut down, upgraded, restarted and the node brought back from maintenance-mode.
The scenario is delicate though as the node still running resources then without
pacemaker-control could still be watchdog-fenced - without any impact on the
node of course. Preventing a node in maintenance-mode from being watchdog-fenced
sounds like a solution here.
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-2020:0995