[ClusterLabs] [Problem] The output of `pcs status --full` is incorrect when a node rejoins.

[Chris Lumens]

> Our users have configured a 5-node cluster using Pacemaker 2.1.9, which is included with RHEL 9.6.

Is this something you just started noticing with pacemaker-2.1.9?

> After successfully building and starting the 5-node cluster, we induced a failure in the fourth node (test4), triggered STONITH, and then rejoined test4 to the cluster.
> When we subsequently ran `pcs status --full` from the fourth node (test4), we observed an issue where resources actually running on nodes test2 and test3 were displayed as "Stopped."

Just to make sure this is definitely a pacemaker problem, can you try 
using the crm_mon command instead of pcs?  So in this case, use
`crm_mon -1r` to get the same output.

Also, am I understanding the situation:

* On the node that was fenced and rejoined, the output is incorrect.
* On all other nodes, the output is correct.

Does the node have to be fenced to cause the problem, or is it enough to 
just bring the node down and back up (either by stopping the cluster on 
that node, putting it in maintainence mode, etc.)?

> Furthermore, the display did not correct itself even after leaving the system for some time.

I imagine this is because there haven't been any CIB changes, so the 
fenced node hasn't received an update.  You could test this by doing 
something that would trigger a CIB update.

> Are you aware of any issues where the display becomes distorted in the version of Pacemaker bundled with RHEL 9.6?
> Alternatively, is there any record of such an issue being resolved in a newer version of Pacemaker?
I'm not aware of anything like this, but I haven't skimmed the bug 
backlog to see if there are any similar reports.  It doesn't sound 
familiar, at least.

- Chris