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

When a setup is configured to manage GFS2 filesystem along with XFS filesystem where active/passive XFS filesystem is configured using `system_id` & `activation_mode=exclusive`, then the `LVM-activate` resource fails to start even when `lvmlockd` resource has started.

It is likely due to the lock manager is not yet started before the start operation is triggered for the `LVM-activate` resource associated with XFS/EXT4 filesystem.

Please provide the package NVR for which bug is seen:

resource-agents-4.9.0-54.el8.x86_64

How reproducible:

Always reproducible

Steps to reproduce

1. Configure two node cluster to manage XFS filesystem using `system_id` & `activation_mode=exclusive` along with GFS2 filesystem using `use_lvmlockd=1` & `lvmlockd` cloned resource

1. Configure the order constraint where the `locking-clone` starts first and then the GFS2 filesystem cloned resource group & XFS filesystem resource group.
   NOTE: There is no start order between GFS & XFS groups

1. Configure a location constraint for XFS group to prefer node1 & set `resource-stickiness` with a value greater than location constraint value.

1. Relocate the XFS resource group to the other node and once relocated, delete the auto-generated location constraint with INFINITY score.

1. Restart the cluster and the `LVM-activate` resource which is managing the XFS filesystem device will fail to activate with following error:
   ```
   {{Apr 23 14:35:26 node1 LVM-activate(web-lv)[1460784]: INFO: Activating cluster_vg
   Apr 23 14:35:26 node1 LVM-activate(web-lv)[1460784]: ERROR: cluster_vg: failed to activate.
   Apr 23 14:35:26 node1 pacemaker-controld[1459385]: notice: Result of start operation for web-lv on node1: error (cluster_vg: failed to activate.)}}
   ```

Expected results

The `LVM-activate` resource managing the device associated with XFS filesystem should be able to get started with lock manager.

Actual results

The `LVM-activate` resource managing the device associated with XFS filesystem fails to start even when the cluster is configured with the order constraint where `lvmlockd` is started fist.