A Filesystem resource fails to start when using device's label in a Pacemaker cluster

Solution Verified - Updated -

Issue

  • Pacemaker's Filesystem resource fails to start with Couldn't mount device error when using the device's label as -L <label_name>:

    # pcs resource create fs ocf:heartbeat:Filesystem device="-L IPXE" directory="/mnt/test" fstype="ext4"
    # pcs resource
      * fs  (ocf::heartbeat:Filesystem):     Stopped
    
    Failed Resource Actions:
      * fs_start_0 on virt-245 'error' (1): call=206, status='complete', exitreason='Couldn't mount device [-L IPXE] as /mnt/test', last-rc-change='Mon May 30 11:51:40 2022', queued=0ms, exec=195ms
    

Environment

  • Red Hat Enterprise Linux Server 8, 9 (with the High Availability Add On)
  • On RHEL 8: resource-agents-4.1.1-90 up to resource-agents-4.9.0-16
  • On RHEL 9: All versions up to resource-agents-4.10.0-9_0.3

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