Why does the `LVM-activate` resource fails to activate the VG with `ERROR: vg_name: failed to activate` ?
Issue
- The active/passive
LVM-activate
resource fails to start when Pacemaker cluster is configured to manage both GFS2 & XFS filesystem with the following error:
Apr 23 14:35:26 node1 LVM-activate(web-lv)[1460784]: INFO: Activating cluster_vg
Apr 23 14:35:26 node1 LVM-activate(web-lv)[1460784]: ERROR: cluster_vg: failed to activate.
Apr 23 14:35:26 node1 pacemaker-controld[1459385]: notice: Result of start operation for web-lv on node1: error (cluster_vg: failed to activate.)
- Even after following the steps in following article, the
LVM-activate
resource for XFS/EXT4 filesystem fails to start: An LVM-activate resource failed to activate with the error: Cannot access VG shared_vg2 with system ID rhel8-1.examplerh.com with local 'system ID rhel8-2.examplerh.com.
Environment
- Red Hat Enterprise Linux 8, 9
- Pacemaker Cluster managing both GFS2 as well as XFS or EXT3/4 filesystems
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.