What were you trying to do that didn't work?  After stopping and restarting Pacemaker on a host, running crm_resource --locate on any resource return "resource <abc> is NOT running".  This seems to be a transient issue as eventually things worked correctly later.

Here is the sequence of events:

• 03:08:26 - Pacemaker was shutdown on host p10rhel095
• 03:12:34 - Start Pacemaker
• 03:14:14 - crm_resource --resource db2_cfprimary_jstamko2 --locate returned "resource db2_cfprimary_jstamko2 is NOT running"

The environment consists of 4 hosts: p10rhel092/93/04/05

What is the impact of this issue to you?  Cluster is not functional after Pacemaker stopped and restarted

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

Pacemaker 2.1.7-4.db2pcmk.el9

How reproducible is this bug?:  Not sure, saw this once but may occur again.

Steps to reproduce

1. Set up a cluster of 4 nodes
2. On one node, stop and restart Pacemaker
3. Run crm_resource --resource <resourceName> --locate immediately after restart

Expected results: Expect that crm_resource to report the correct resource state and location

Actual results: crm_resource returned source as NOT running