Pacemaker cluster fails to activate LVM resource when there are no logical volumes in the volume group

Solution Verified - Updated -

Issue

  • Pacemaker cluster fails to activate LVM resource when there are no logical volumes in the volume group
Jul  2 16:51:25 node1 LVM(cluster_vg)[908]: INFO: Activating volume group cluster_vg
Jul  2 16:51:25 node1 LVM(cluster_vg)[908]: INFO: Reading all physical volumes. This may take a while... Found volume group "localvg" using metadata type lvm2 Found volume group "vg00" using metadata type lvm2 Found volume group "cluster_vg" using metadata type lvm2 Found volume group "vg2" using metadata type lvm2
Jul  2 16:51:25 node1 LVM(cluster_vg)[908]: INFO: 0 logical volume(s) in volume group "vgsrc1" now active
Jul  2 16:51:25 node1 LVM(cluster_vg)[908]: ERROR: LVM Volume cluster_vg is not available (stopped)
Jul  2 16:51:25 node1 LVM(cluster_vg)[908]: ERROR: LVM: vgsrc1 did not activate correctly
Failed Actions:
* cluster_vg_start_0 on node2 'not running' (7): call=66, status=complete, exitreason='LVM: cluster_vg did not activate correctly',
    last-rc-change='Mon Jul  2 16:52:34 2018', queued=0ms, exec=561ms
* cluster_vg_start_0 on node1 'not running' (7): call=68, status=complete, exitreason='LVM: cluster_vg did not activate correctly',
    last-rc-change='Mon Jul  2 16:52:34 2018', queued=0ms, exec=500ms

Environment

  • Red Hat Enterprise Linux Server 6, 7 (with the High Availability Add-on)
  • Pacemaker

Subscriber exclusive content

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

Current Customers and Partners

Log in for full access

Log In