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 1972273 - pacemaker seems to end up in an unfence loop [rhel-8.4.0.z]
Summary: pacemaker seems to end up in an unfence loop [rhel-8.4.0.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pacemaker
Version: 8.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: beta
: ---
Assignee: Ken Gaillot
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1961857
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-15 14:39 UTC by RHEL Program Management Team
Modified: 2022-09-13 14:36 UTC (History)
9 users (show)

Fixed In Version: pacemaker-2.0.5-9.el8_4.2
Doc Type: Bug Fix
Doc Text:
Cause: Pacemaker's controller on a node might be elected the Designated Controller (DC) before its attribute manager learned an already-active remote node is remote. Consequence: The node's scheduler would not see any of the remote node's node attributes. If the cluster used unfencing, this could result in an unfencing loop. Fix: The attribute manager can now learn a remote node is remote via additional events, including the initial attribute sync at start-up. Result: No unfencing loop occurs, regardless of which node is elected DC.
Clone Of: 1961857
Environment:
Last Closed: 2021-09-21 08:39:48 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 6534751 0 None None None 2022-09-13 14:36:17 UTC
Red Hat Product Errata RHBA-2021:3578 0 None None None 2021-09-21 08:39:54 UTC

Comment 1 Ken Gaillot 2021-06-22 16:45:15 UTC
Fixed upstream as of commit 540d7413

Comment 3 Julia Marciano 2021-08-02 13:19:55 UTC
Verified:
After the fixed (pacemaker-2.0.5-9.el8_4.2)  packages were installed on controller and compute nodes, and after executing all issue-reproducing steps (please see [Steps] below), it seems that the issue doesn't reproduce anymore. No spurious, node-unfenced related messages were found in the pacemaker log:
(undercloud) [stack@undercloud-0 ~]$ for i in $(openstack server list -c Networks -f value | cut -f2 -d\=); do  ssh $i "hostname; rpm -q pacemaker; sudo grep -e 'Cannot update #node-unfenced' /var/log/pacemaker/pacemaker.log"; done 2>/dev/null
controller-1
pacemaker-2.0.5-9.el8_4.2.x86_64
controller-0
pacemaker-2.0.5-9.el8_4.2.x86_64
controller-2
pacemaker-2.0.5-9.el8_4.2.x86_64
compute-1
pacemaker-2.0.5-9.el8_4.2.x86_64
compute-0
pacemaker-2.0.5-9.el8_4.2.x86_64

[Steps]:
1. cont-1# sudo shutdown -h now   // curent-DC was cont-0
2. comp-0# sudo reboot
3. openstack baremetal node power on <cont-1 UUID>
4.  Wait for cluster to include cont-1
5. cont-0# echo b > /proc/sysrq-trigger  --> cont-2 became a DC
6. cont-2# echo b > /proc/sysrq-trigger -->  cont-1 became a DC

Comment 14 errata-xmlrpc 2021-09-21 08:39:48 UTC
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 (pacemaker bug fix and enhancement update), 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-2021:3578


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