What were you trying to do that didn't work? After gracefully reboot of a node (using reboot command with no option), the node came back online but was shutdown shortly after.

1. Cluster consists of 5 nodes: svlzps11 svlzps12 svlzps13 svlzps14 svlzps15

2. Reboot nodes svlzps13 at  2025-11-24-17.51.12

3. Reboot node svlzps14 at  2025-11-24-17.51.14

4. Node svlzps14 rejoined at 17:52:06

Nov 24 17:53:06.293 svlzps12 pacemaker-controld  [5794] (peer_update_callback)  info: Node svlzps14 is now a peer | DC=svlzps12 old=0000000 new=0x4000000

5. Node svlzps14 then got shut down by the DC (svlzps12) at 17:52:07

Nov 24 17:53:07.643 svlzps12 pacemaker-schedulerd[5793] (determine_online_status)       info: svlzps14 is shutting down

Nov 24 17:53:07.653 svlzps12 pacemaker-schedulerd[5793] (node_action)   notice:  * Shutdown svlzps14

What is the impact of this issue to you?  Node down.

Please provide the package NVR for which the bug is seen: 2.1.10

How reproducible is this bug?: intermittent

Steps to reproduce

1. Set up a Pacemaker cluster with multiple (5) nodes
2. Run reboot command on one of the host
3.  

Expected results: Node automatically rejoined the cluster successfully

Actual results:  Node rejoined, but was unexpected shutdown shortly after