Galera resource in cluster fails to start and reports "Could not determine galera name"

Issue

During start operations a galera cloned resources fails to start on one or all nodes. While failing to start it reports the below errors:

• Observed in pcs status output:

  $ pcs status --full
  Node List:
    * Online: [ rhel8-node1 (1) rhel8-node2 (2) rhel8-node3 (3) ]
  -----------------------------------------8<----------------------------------------- 
  Migration Summary:
    * Node: galera-bundle-0@rhel8-node3:
      * galera: migration-threshold=1000000 fail-count=1000000 last-failure='Tue Nov 26 21:16:01 2024'
  
  Failed Resource Actions:
    * galera_start_0 on galera-bundle-0 'not configured' (6): call=49, status='complete', exitreason='Could not determine galera name from pacemaker node <rhel8-node3>.', last-rc-change='2024-11-26 21:16:01Z', queued=0ms, exec=149ms
  

• Observed in /var/log/messages:

  Nov 25 16:18:21 rhel8-node3 pacemaker-controld[3886]: notice: Requesting local execution of start operation for galera on galera-bundle-0
  Nov 25 16:18:22 rhel8-node3 galera(galera)[87]: ERROR: Could not determine galera name from pacemaker node <rhel8-node3>.
  Nov 25 16:18:22 rhel8-node3 pacemaker-remoted[7]: notice: galera_start_0[87] error output [ ocf-exit-reason:Could not determine galera name from pacemaker node <rhel8-node3>. ]
  Nov 25 16:18:22 rhel8-node3 pacemaker-controld[3886]: notice: Result of start operation for galera on galera-bundle-0: not configured
  Nov 25 16:18:22 rhel8-node3 pacemaker-controld[3886]: notice: galera-bundle-0-galera_start_0:12 [ ocf-exit-reason:Could not determine galera name from pacemaker node <rhel8-node3>.\n ]
  

Once the above error is observed, the resource is considered not configured and the galera resource is blocked from starting.