LVM errors from pacemaker on nodes where storage is not attached permanently

Solution In Progress - Updated -

Issue

  • Our High Availability / Resilient Storage the cluster contains nodes where the storage is not always attached
  • Upon running pcs resource cleanup, we receive errors
Sep 13 16:44:13 node3 lrmd[2838]:  notice: HA_VG-resource_monitor_0:30005:stderr [ ocf-exit-reason:LVM Volume HA_VG is not available ]
Sep 13 16:44:13 node3 crmd[20303]:  notice: Result of probe operation for HA_VG-resource on node3: 1 (unknown error)
Sep 13 16:44:13 node3 crmd[20303]:  notice: node3-HA_VG-resource_monitor_0:2111 [ ocf-exit-reason:LVM Volume HA_VG is not available\n ]

Environment

  • Red Hat Enterprise Linux 7 with High Availability Add-On
  • Red Hat Enterprise Linux 7 with 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