LVM-activate resource with vg_access_mode=lvmlockd doesn't start after reboot

Solution Verified - Updated -

Issue

  • LVM-activate resource with vg_access_mode=lvmlockd doesn't start after the node reboots or the pacemaker service is restarted.
  • LVM-activate resource fails probe with "not configured" error.
[root@rhel-7-0-3 ~]# pcs status --full
...
 Clone Set: locking-clone [locking]
     Resource Group: locking:0
         dlm    (ocf::pacemaker:controld):  Started rhel-7-0-3
         lvmlockd   (ocf::heartbeat:lvmlockd):  Started rhel-7-0-3
     Resource Group: locking:1
         dlm    (ocf::pacemaker:controld):  Started rhel-7-0-4
         lvmlockd   (ocf::heartbeat:lvmlockd):  Started rhel-7-0-4
     Started: [ rhel-7-0-3 rhel-7-0-4 ]
 Clone Set: clusterfs_grp-clone [clusterfs_grp]
     Resource Group: clusterfs_grp:0
         my_lvm (ocf::heartbeat:LVM-activate):  Stopped
         clusterfs  (ocf::heartbeat:Filesystem):    Stopped
     Resource Group: clusterfs_grp:1
         my_lvm (ocf::heartbeat:LVM-activate):  Stopped
         clusterfs  (ocf::heartbeat:Filesystem):    Stopped
     Stopped: [ rhel-7-0-3 rhel-7-0-4 ]
...
Failed Resource Actions:
* my_lvm_monitor_0 on rhel-7-0-3 'not configured' (6): call=20, status=complete, exitreason='lvmlockd daemon is not running!',
    last-rc-change='Fri Dec 28 21:43:53 2018', queued=0ms, exec=261ms

Environment

  • Red Hat Enterprise Linux 7 with the High Availability Add-on
  • lvmlockd
  • An LVM-activate resource

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