An ocf:heartbeat:clvm resource doesn't activate all clustered volume groups in a Pacemaker cluster

Solution Verified - Updated -

Issue

  • When a clvmd resource started, it didn't activate all of the clustered volume groups.
  • In the example below, all volume groups except vg_OS have the clustered bit set, and many of them did not get activated when the ocf:heartbeat:clvm resource started.
May 23 02:38:56 node1 clvm(clvmd)[5606]: INFO: 0 logical volume(s) in volume group "vg_rhvm4_DGA_DATA" now active 1 logical volume(s) in volume group "vg_rhv4_3T_DRP" now active 1 logical volume(s) in volume group "vg_rhvm4_3T_DATA" now active 1 logical volume(s) in volume group "vg_rhvm4_3T_OS" now active 0 logical volume(s) in volume group "vg_3T_OVM2" now active 0 logical volume(s) in volume group "vg_3T_OVM_PIVOTE" now active 0 logical volume(s) in volume group "vg_rhvm4_DGA_OS" now active 1 logical volume(s) in volume group "vg_3T_OVM" now active 5 logical volume(s) in volume group "vg_OS" now active

Environment

  • Red Hat Enterprise Linux 7 (with the Resilient Storage 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