-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-10.2
-
None
-
None
-
None
-
rhel-storage-lvm
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
-
x86_64
-
None
After PR is set up and running on the primary node, attempting to enable it again on the secondary node fails with what appears to be a cryptic problem. In reality, it's a no-op since the enablement is done on a per VG basis and already exists in the metadata. All that is needed is for the secondary node to start persist and then to start locking.
kernel-6.12.0-165.el10 BUILT: Fri Nov 28 09:08:39 AM CET 2025 lvm2-2.03.36-1.el10 BUILT: Sat Oct 25 04:42:32 AM CEST 2025 lvm2-libs-2.03.36-1.el10 BUILT: Sat Oct 25 04:42:32 AM CEST 2025 # PRIMARY NODE SET UP OPERATIONS vgcreate --shared persist_VG /dev/sda /dev/sdb /dev/sdc /dev/sdd /dev/sde Enabling sanlock global lock Logical volume "lvmlock" created. Volume group "persist_VG" successfully created VG persist_VG starting sanlock lockspace Starting locking. Waiting until locks are ready... changing 'vgchange --setpersist y persist_VG' on virt-498.cluster-qe.lab.eng.brq.redhat.com changing 'vgchange --persist start persist_VG' on virt-498.cluster-qe.lab.eng.brq.redhat.com lvcreate --yes --type linear -n persist_LV_primary -L 600M persist_VG Logical volume "persist_LV_primary" created. # SECONDARY NODE SET UP OPERATION ATTEMPT changing 'vgchange --setpersist y persist_VG' on virt-499.cluster-qe.lab.eng.brq.redhat.com Device /dev/sda has PVID GwI31sfpZGyBskpPbBDKrvrXzVyv044F (devices file aS2TesODgTxwaanJkUhIF79xycKfU0xi) Device /dev/sdb has PVID KR9TgMtonEVkIjkQeVCAkdie1yQbcaW8 (devices file ZmPKJES8mdHc0ZbIvTtCWbh3t9OT0Qmk) Device /dev/sdc has PVID 0hwDjEKZgtYJrAgT8nuq4U3b9J4CrPk0 (devices file 5AXA00oRPmWzzNLmFW7AcdV6GNLOTQtG) Device /dev/sdd has PVID Z3pxe4fkc7N0aeeyWAc7r6g79LvEMUtX (devices file hwss6CFIOqzkO3DYBZfDF7nVEzwYmfh5) Device /dev/sde has PVID SJ6wOWswLhZGY38P61WgSsIqcBt7krRg (devices file ZtVzt5S28A7l4nCJ8MXKlQ5IlX4SdEz6) Cannot access VG persist_VG due to failed lock. # SECONDARY NODE SET UP OPERATIONS changing 'vgchange --persist start persist_VG' on virt-499.cluster-qe.lab.eng.brq.redhat.com starting VG locking on virt-499.cluster-qe.lab.eng.brq.redhat.com vgchange --lockstart persist_VG VG persist_VG starting sanlock lockspace Starting locking. Waiting for sanlock may take a few seconds to 3 min... lvcreate --yes --type linear -n persist_LV_secondary -L 600M persist_VG Logical volume "persist_LV_secondary" created.
