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

[renayama19661014 at ybb.ne.jp]

Hi All,

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

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." 
* In the output below, `primary-group2` and `primary-group3` appear as "Stopped," but when checked from a node like test1, they are actually running on test2 and test3.

Furthermore, the display did not correct itself even after leaving the system for some time. 
* This issue does not occur 100% of the time; the status is sometimes displayed correctly.

---
# pcs status --full
(snip)
Node List:
   * Node test1 (1): online, feature set 3.19.6
   * Node test2 (2): online, feature set 3.19.6
   * Node test3 (3): online, feature set 3.19.6
   * Node test4 (4): online, feature set 3.19.6
   * Node test5 (5): online, feature set 3.19.6
 
Full List of Resources:
   * Resource Group: primary-group1:
    * ipaddr_gwf_101  (ocf:heartbeat:IPaddr2):         Started test1
    * ipaddr_dbf_101  (ocf:heartbeat:IPaddr2):         Started test1
    * ipaddr_api_101  (ocf:heartbeat:IPaddr2):         Started test1
    * ipaddr_kafka_101        (ocf:heartbeat:IPaddr2):         Started test1
    * ipaddr_unyo_101 (ocf:heartbeat:IPaddr2):         Started test1
    * fs_share_101    (ocf:heartbeat:Filesystem):      Started test1
    * mw_jp1base_101  (ocf:jp1:ra_jp1base):    Started test1
    * mw_jp1ajs3_101  (ocf:jp1:ra_jp1ajs3):    Started test1
  * Resource Group: primary-group2:
    * ipaddr_gwf_102  (ocf:heartbeat:IPaddr2):         Stopped
    * ipaddr_dbf_102  (ocf:heartbeat:IPaddr2):         Stopped
    * ipaddr_api_102  (ocf:heartbeat:IPaddr2):         Stopped
    * ipaddr_kafka_102        (ocf:heartbeat:IPaddr2):         Stopped
    * ipaddr_unyo_102 (ocf:heartbeat:IPaddr2):         Stopped
    * fs_share_102    (ocf:heartbeat:Filesystem):      Stopped
    * mw_jp1base_102  (ocf:jp1:ra_jp1base):    Stopped
    * mw_jp1ajs3_102  (ocf:jp1:ra_jp1ajs3):    Stopped
  * Resource Group: primary-group3:
    * ipaddr_gwf_103  (ocf:heartbeat:IPaddr2):         Stopped
    * ipaddr_dbf_103  (ocf:heartbeat:IPaddr2):         Stopped
    * ipaddr_api_103  (ocf:heartbeat:IPaddr2):         Stopped
    * ipaddr_kafka_103        (ocf:heartbeat:IPaddr2):         Stopped
    * ipaddr_unyo_103 (ocf:heartbeat:IPaddr2):         Stopped
    * fs_share_103    (ocf:heartbeat:Filesystem):      Stopped
    * mw_jp1base_103  (ocf:jp1:ra_jp1base):    Stopped
    * mw_jp1ajs3_103  (ocf:jp1:ra_jp1ajs3):    Stopped
  * Clone Set: ping-clone [ping]:
    * ping    (ocf:pacemaker:ping):    Started test4
    * ping    (ocf:pacemaker:ping):    Started test1
    * ping    (ocf:pacemaker:ping):    Stopped
    * ping    (ocf:pacemaker:ping):    Stopped
    * ping    (ocf:pacemaker:ping):    Stopped
  * Clone Set: storage-mon-clone [storage-mon]:
    * storage-mon     (ocf:heartbeat:storage-mon):     Started test4
    * storage-mon     (ocf:heartbeat:storage-mon):     Started test1
    * storage-mon     (ocf:heartbeat:storage-mon):     Stopped
    * storage-mon     (ocf:heartbeat:storage-mon):     Stopped
    * storage-mon     (ocf:heartbeat:storage-mon):     Stopped
  * fence_sbd_101     (stonith:fence_sbd):     Stopped
  * fence_sbd_102     (stonith:fence_sbd):     Stopped
  * fence_sbd_103     (stonith:fence_sbd):     Stopped

---
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?

Best Regards,
Hideo Yamauchi.