NVME storage starts after pacemaker tries to start LVM resources in the cluster, which results in an error: Volume group[myvg1] doesn't exist, or not visible on this node!

Solution Verified - Updated -

Issue

  • NVME storage starting after pacemaker means that when pacemaker is trying to bring up the LVM resources, it gets an error about the volume groups not existing.
    In this case the NVME discovery controller is different than the controller that is actually presenting the LUNs.
Mar 18 03:45:54 hostname LVM-activate(cluster_lv_2)[3711]: ERROR: Volume group[cluster_vg_2] doesn't exist, or not visible on this node!
Mar 18 03:45:54 hostname LVM-activate(cluster_lv_1)[3712]: ERROR: Volume group[cluster_vg_1] doesn't exist, or not visible on this node!

Environment

  • Red Hat Enterprise Linux
    • Pacemaker cluster

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