Back to bug 2228933
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2023-08-03 16:57:54 UTC | Pool ID | sst_high_availability_rhel_9 | |
| Red Hat One Jira (issues.redhat.com) | 2023-08-03 16:59:02 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-164410 | |
| Ken Gaillot | 2023-08-03 17:05:10 UTC | Target Release | --- | 9.3 |
| Target Upstream Version | 2.1.7 | |||
| Keywords | Triaged | |||
| Status | NEW | ASSIGNED | ||
| Priority | unspecified | urgent | ||
| Severity | medium | urgent | ||
| Doc Text | Cause: A node's attribute manager is eligible to become the attribute writer even if shutdown has been requested for the node. Consequence: If a node is DC, begins the shutdown sequence, 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 be eligible for election as attribute writer if shutdown has been requested for its node. Result: A leaving DC node does not have an unexpected shutdown the next time it rejoins. | |||
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Ken Gaillot | 2023-08-03 17:31:48 UTC | Doc Text | Cause: A node's attribute manager is eligible to become the attribute writer even if shutdown has been requested for the node. Consequence: If a node is DC, begins the shutdown sequence, 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 be eligible for election as attribute writer if shutdown has been requested for its node. Result: A leaving DC node does not have an unexpected shutdown the next time it rejoins. | 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. |
| Ken Gaillot | 2023-08-03 18:06:09 UTC | Blocks | 2228955 | |
| Chris Feist | 2023-08-03 22:29:30 UTC | CC | cfeist | |
| RHEL Program Management Team | 2023-08-03 22:31:21 UTC | Blocks | 2229014 | |
| RHEL Program Management Team | 2023-08-03 22:31:25 UTC | Keywords | ZStream | |
| Ken Gaillot | 2023-08-03 22:36:40 UTC | Status | ASSIGNED | POST |
| Markéta Smazová | 2023-08-04 13:13:47 UTC | CC | msmazova | |
| Dean Jansa | 2023-08-04 14:17:05 UTC | Link ID | Red Hat Issue Tracker CLUSTERQE-6845 | |
| Ken Gaillot | 2023-08-09 14:40:15 UTC | CC | jmarcian | |
| Chris Lumens | 2023-08-09 15:56:37 UTC | Status | POST | MODIFIED |
| errata-xmlrpc | 2023-08-09 18:07:04 UTC | Fixed In Version | pacemaker-2.1.6-8.el9 | |
| Status | MODIFIED | ON_QA | ||
| Red Hat Bugzilla | 2023-08-10 15:41:36 UTC | QA Contact | cluster-qe | cluster-qe |
Back to bug 2228933