Back to bug 2000595

Who When What Removed Added
Red Hat Bugzilla 2021-09-02 13:11:00 UTC Pool ID sst_high_availability_rhel_8
Red Hat One Jira (issues.redhat.com) 2021-09-02 13:12:06 UTC Link ID Red Hat Issue Tracker RHELPLAN-95999
Ken Gaillot 2021-09-03 19:14:26 UTC Doc Type --- If docs needed, set a value
Ken Gaillot 2021-09-09 22:13:38 UTC Flags needinfo?(tbskyd)
tbsky 2021-09-10 01:55:40 UTC Flags needinfo?(tbskyd)
Ken Gaillot 2021-09-10 19:40:13 UTC OS Unspecified All
Hardware Unspecified All
Keywords Triaged
Priority unspecified medium
Reid Wahl 2022-12-22 01:18:56 UTC CC nwahl
RHEL Program Management 2023-03-02 07:27:49 UTC Status NEW CLOSED
Resolution --- WONTFIX
Last Closed 2023-03-02 07:27:49 UTC
Reid Wahl 2023-03-02 08:02:11 UTC Resolution WONTFIX ---
Status CLOSED NEW
Keywords Reopened
Ken Gaillot 2023-06-15 16:27:06 UTC Status NEW POST
Doc Text Cause: When a node joined the cluster, Pacemaker previously erased its known resource history and updated it with the current known status in two separate steps.

Consequence: If "pcs status" were run between the two steps, it would wrongly appear that no resources were active on the joining node.

Fix: The erase and update are now done in a single CIB modification.

Result: "pcs status" always shows the correct known state
Target Release --- 8.10
Target Upstream Version 2.1.7
Assignee kgaillot nwahl
Doc Type If docs needed, set a value Bug Fix
Red Hat Bugzilla 2023-08-10 15:41:25 UTC QA Contact cluster-qe cluster-qe

Back to bug 2000595