Jonathan,

Looking at the agent, this situation appears to be by design. Can you comment on why this limitation exists please.

-- Vossel

I researched this a bit. It looks like this limitation is just for the tagging use-case.  When clvm is used I believe this works like you would expect it to.

I think this limitation is set in place to make it difficult to potentially activate a volume group in two places (which would happen if vg had multiple lv being activated on different nodes) when clvm is not in use.

-- Vossel

I've talked to Jonathan Brassow about this and here is our conclusion to why this limitation exists.

With exclusive activation using tags, the only safe way to activate a logical volume without cLVM is to guarantee both the volume group and all the logical volumes in that volume group are activated on a single node.

This means we can only safely allow activation by logical volume (using tags) if that logical volume is the only one in the volume group. Otherwise we run the risk of parallel activation of two logical volumes in the same volume group occurring on separate nodes, which could corrupt the volume group metadata.

I agree that the limitations is weird. Right now I'm in the process of merging the redhat lvm.sh agent with the heartbeat LVM agent.  Since activating my lv offers us nothing we can't do with activating by vg when tags are in use, I am going to disable activation by logical volumes for non-cluster volume groups.

So, moving forward.

Activation by LV = only clustered volume groups.  This will be documented and enforced after the lvm.sh merger into the heartbeat provider.

We can leave this issue open until I finish the lvm.sh merger into the heartbeat provider, or close it. Whatever makes the most sense for you all.

-- Vossel

Makes sense to me. Let's keep the bug open until lvm.sh is merged.

Activation by logical volume will not be supported in the new pacemaker heartbeat:LVM agent.  The LVM agent's use-cases for activation by volume group are already complex.  The inclusion of activation by logical volume imposed additional complications and limitations on the user that we neither want to document or support.  These limitations where not well understood when the logical volume feature existed in the rgmanager agent until later on.  Now that we have a chance to break compatibility, this option will not be carried over.

-- info on exclusive activation copied from 960555 --

The heartbeat:LVM agent now performs exclusive activation with tags for rhel7 instead of redhat:lvm.sh. This new agent works slightly different than the rgmanager one.

For exclusive activation to work, the 'exclusive' option must be set to true, and the 'volume_list' in lvm.conf must be defined.  The resource agent doesn't care what the volume_list is defined to as long as the special cluster tag "@pacemaker" and the volume group are not present in the list.  volume_list=[] would even work as a minimal config.

Volume groups are exclusively activated by having the the '@pacemaker' tag added to them by the resource agent.  On activation, the 'volume_list' is overridden by the resource agent to allow volume groups with the '@pacemaker' tag to be enabled. Outside of the resource agent, the volume_list defined in lvm.conf that does _NOT_ container '@pacemaker' or the volume group prevents the volume group from being activated outside of the cluster control. 

The upstream patch below is related to this issue.
https://github.com/ClusterLabs/resource-agents/commit/d7274446d79757d436b972892f00339fc28da13e

ocf:redhat:lvm.sh has been replaced with ocf:heartbeat:LVM  which implements what is in an initial report correctly. 

ocf:redhat:LVM from resource-agents-3.9.5-18 has been tested.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.