What were you trying to do that didn't work?  

The cluster consists of 2 quorum nodes and 2 Pacemaker remote nodes.  When a quorum node was fenced (this is part of the testing), the Pacemaker remote resource that was running on that node migrated to run on the other quorum node.  However, it failed to restart with this error as seen the pacemaker.log file:
Apr 25 11:40:18.247 ps-4 pacemaker-schedulerd[3072816] (unpack_rsc_op) error: Preventing ps-1 from restarting on ps-4 because of hard failure (invalid parameter: Key was rejected by service) | ps-1_last_failure_0

Please provide the package NVR for which bug is seen: 

Pacemaker 2.1.6-4.db2pcmk.el9

How reproducible: Frequent

Steps to reproduce

1. Set up a cluster with 2 quorum nodes and 2 Pacemaker remote node, with fencing agent define to perform the fencing.
2. Run ifconfig <eth> down to take down the main interface on one quorum node
3. The Pacemaker remote resource that was running on the fenced node, migrated to run on the other quorum node but failed to start.

Expected results: Pacemaker remote resource migrated successfully

Actual results: Pacemaker remote resource failed to start and stayed in stopped state.

pcmk-Thu-25-Apr-2024.tar.bz2