Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cloning this for rhel8.1
In prior rhel7 releases we could definitely check for the timestamp (sanlock client host_status -s lvm_$vg | grep -vE \"timestamp 0\") to tick to 0 on the node with the lock remaining after it had been stopped on the others, and we knew we could safely remove/alter the VG. That timestamp appears to be missing in rhel8 now, so were back to checking that the lock is gone with sanlock client host_status, then waiting an arbitrary amount of time and crossing fingers.
[root@host-087 ~]# vgremove -f global
Lockspace for "global" not stopped on other hosts
[root@host-087 ~]# vgremove -f global
Lockspace for "global" not stopped on other hosts
[root@host-087 ~]# vgremove -f global
Lockspace for "global" not stopped on other hosts
[root@host-087 ~]# vgremove -f global
Lockspace for "global" not stopped on other hosts
[root@host-087 ~]# vgremove -f global
Lockspace for "global" not stopped on other hosts
[root@host-087 ~]# vgremove -f global
Volume group "global" successfully removed
kernel-4.18.0-147.el8 BUILT: Thu Sep 26 11:15:44 CDT 2019
lvm2-2.03.05-5.el8 BUILT: Thu Sep 26 01:40:57 CDT 2019
lvm2-libs-2.03.05-5.el8 BUILT: Thu Sep 26 01:40:57 CDT 2019
lvm2-dbusd-2.03.05-5.el8 BUILT: Thu Sep 26 01:43:33 CDT 2019
lvm2-lockd-2.03.05-5.el8 BUILT: Thu Sep 26 01:40:57 CDT 2019
device-mapper-1.02.163-5.el8 BUILT: Thu Sep 26 01:40:57 CDT 2019
device-mapper-libs-1.02.163-5.el8 BUILT: Thu Sep 26 01:40:57 CDT 2019
device-mapper-event-1.02.163-5.el8 BUILT: Thu Sep 26 01:40:57 CDT 2019
device-mapper-event-libs-1.02.163-5.el8 BUILT: Thu Sep 26 01:40:57 CDT 2019
device-mapper-persistent-data-0.8.5-2.el8 BUILT: Wed Jun 5 10:28:04 CDT 2019
sanlock-3.8.0-2.el8 BUILT: Wed Jun 12 15:50:27 CDT 2019
sanlock-lib-3.8.0-2.el8 BUILT: Wed Jun 12 15:50:27 CDT 2019
I don't think this is important enough to open up new development for (it's not trivial). If I'm doing development in this area in the future I'll look at doing it.