Bug 2229013
| Summary: | Race condition when DC and attribute writer are both shutting down [rhel-8.8.0.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | RHEL Program Management Team <pgm-rhel-tools> |
| Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 8.4 | CC: | cfeist, cluster-maint, mjuricek, msmazova |
| Target Milestone: | rc | Keywords: | Triaged, ZStream |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | pacemaker-2.1.5-9.3.el8_8 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: A node's attribute manager writes all its transient node attributes from memory to the CIB after winning the election for attribute writer, even if its node has requested shutdown.
Consequence: If a node is DC, requests shutdown, and wins the attribute writer election after its controller has left the cluster but before its attribute manager has left, it can write out its shutdown attribute to the CIB. The next time it rejoins the cluster, it will be immediately shut down.
Fix: A node's attribute manager should not write out its attributes after winning an election if shutdown has been requested for its node.
Result: A leaving DC node does not have an unexpected shutdown the next time it rejoins.
|
Story Points: | --- |
| Clone Of: | 2228955 | Environment: | |
| Last Closed: | 2023-09-19 14:36:51 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2228955 | ||
| Bug Blocks: | |||
|
Comment 1
Ken Gaillot
2023-08-03 22:34:57 UTC
Completed fix has been merged in upstream main branch as of commit 58400e27 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 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-2023:5261 |