Bug 1975388
Summary: | pacemaker seems to end up in an unfence loop | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Ken Gaillot <kgaillot> |
Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | cluster-qe <cluster-qe> |
Severity: | high | Docs Contact: | Steven J. Levine <slevine> |
Priority: | high | ||
Version: | 9.0 | CC: | cluster-maint, dabarzil, msmazova, presharm |
Target Milestone: | beta | Keywords: | Triaged |
Target Release: | 9.0 Beta | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | pacemaker-2.1.0-5.el9 | Doc Type: | Bug Fix |
Doc Text: |
.Pacemaker attribute manager correctly determines remote node attributes, preventing unfencing loops
Previously, 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. When this occurred, 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. With the fix, the attribute manager can now learn a remote node is remote by means of additional events, including the initial attribute sync at start-up. As a result, no unfencing loop occurs, regardless of which node is elected DC.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2021-12-07 21:57:54 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ken Gaillot
2021-06-23 14:53:07 UTC
Since this was originally a RHOSP-related bz, RHOSP has verified the corresponding 8.4.z Bug 1972273, and this can get sanity-only testing |