A volume group managed by an LVM-activate resource is active on multiple nodes in a Pacemaker cluster

Issue

• A volume group managed by an LVM-activate resource is active on node1 even though it has node2's system ID attached to it. It should not be allowed to activate on node1.
• A cluster-managed volume group gets activated at boot time by the lvm2-pvscan service.
• After Pacemaker started on a node that had just been fenced, the scheduler logged a message like the following for an LVM-activate resource with vg_access_mode=system_id:

Mar 18 14:56:13 node1 pacemaker-schedulerd[4757]: error: Resource halvm is active on 2 nodes (attempting recovery)