VG under cluster fails to get activated on the node which had HBA replaced and cluster is configured with IO fence

Solution Verified - Updated -

Issue

  • Although fence_mpath reported for a successful unfence operation, the LVM resource fails to start on the node where HBA was replaced.
  • Post replacing the HBA of cluster managed shared storage device on one of the cluster node, the VG fails to activate on the same node.

Environment

  • Red Hat Enterprise Linux 7,8
  • Pacemaker Cluster setup
  • fence_mpath fence agent configured

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