LVM resource using system_id failing to start in RHEL 8.

Solution In Progress - Updated -

Issue

  • LVM resource is failing to start using system_id
  • pcs status keeps showing LVM resource status as FAILED and Monitoring.

    Resource Group: HA-LVM:
        * vg-systemid1      (ocf::heartbeat:LVM-activate):   FAILED node1.example.com (Monitoring)
    
  • pcs status shows monitor operation is not running on LVM resource.

    Failed Resource Actions:
       * vg-systemid1_monitor_60000 on node1.example.com 'not running' (7): call=4695, status='complete', exitreason='', last-rc-change='2020-10-28 19:36:58 +05:30', queued=0ms, exec=14ms
    
    Oct 28 19:36:58 halvm3 pacemaker-schedulerd[1324]: warning: Unexpected result (not running) was recorded for monitor of vg-systemid1 on node1.example.com at Oct 28 19:36:57 2020
    Oct 28 19:36:58 halvm3 pacemaker-schedulerd[1324]: warning: Unexpected result (not installed: Couldn't find device [/dev/systemid1/systemid1lv]. Expected /dev/??? to exist) was recorded for start of fs-systemid1 on node1.example.com at Oct 28 19:36:52 2020
    

Environment

  • Red Hat Enterprise Linux 8
  • High Availability and/or Resilient Storage Add-On
  • Active/Passive configuration for Shared Storage

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