LVM resource restarts when a node rejoins the cluster without shared storage presented in RHEL High Availability or Resilient Storage cluster

Solution Unverified - Updated -

Issue

When a node joins an active cluster without all shared storage devices presented, LVM resources running on already active nodes restart with the following error:

Dec 10 07:33:56 [11743] node1    pengine:    error: native_create_actions:    Resource my_vg (ocf:heartbeat:LVM) is active on 2 nodes attempting recovery
Dec 10 07:33:56 [11743] node1    pengine:  warning: native_create_actions:    See http://clusterlabs.org/wiki/FAQ#Resource_is_Too_Active for more information.
Dec 10 07:33:56 [11743] node1    pengine:   notice: LogActions:       Restart my_vg    (Started node1)

The initializing node shows this error when probing LVM resources backed by storage not currently presented to it:

Dec 10 07:33:56 node2 crmd[2198]:  notice: Result of probe operation for my_vg on node2: 1 (unknown error)
Dec 10 07:33:56 node2 crmd[2198]:  notice: node2-my_vg_monitor_0:29 [ ocf-exit-reason:LVM Volume IO is not available\n ]

Environment

  • Red Hat Enterprise Linux 7 w/ HA or RS Add-On

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content