LVM resource and associated resources restart in place when a node joins the cluster rather than continuing to run on that node or relocating to the other node in a RHEL 6 High Availability cluster with pacemaker

Solution Unverified - Updated 2014-07-03T16:50:12+00:00 -

Issue

Once a failed or rebooted node rejoins the cluster, the resource group gets restarted on same node where it is currently active, which is strange as it should not restart there.
When a node joins the cluster, the service stops and then starts back up in place. Why does it not just stay running? If its restarting, why does it not move to the other node?

Red Hat Enterprise Linux (RHEL) 6 with the Resilient Storage Add On
pacemaker
lvm2-cluster
- locking_type = 3 in /etc/lvm/lvm.conf
- One or more volume group with the clustered ('c') attribute set
- clvmd chkconfig'd on
ocf:heartbeat:LVM resource(s) in cluster configuration
- exclusive=false
- volgrpname corresponds to a clustered volume group
- Resource is not cloned
- The resource has either
  - resource-stickiness set to a value greater than zero (or pcs resource defaults shows a default value greater than 0), or
  - A constraint exists that causes this resource or the group its in to prefer a specific node

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.