LVM Failed actions occurring on the node where the LVM resource is not running

Solution Verified - Updated -

Issue

  • Failed actions occurring for LVM resources on the node where they are not running.
    Example:
Failed Actions:
* resource_lvm_monitor_0 on node1 'unknown error' (1): call=1903, status=complete, exitreason='LVM Volume <vg-name> is not available',
    last-rc-change='Fri Sep 15 16:07:44 2017', queued=0ms, exec=98ms
"LVM Volume <vg-name> is not available".

Environment

  • Red Hat Enterprise Linux 7 with High-Availability or Resilient Storage Add-on
  • Pacemaker
  • resource-agents-3.9.5-105.el7 or possibly earlier versions
  • lvm2-2.02.130-5.el7 or possibly earlier versions

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

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.