Hide Forgot
Description of problem: This low priority issue was actually mentioned in: https://bugzilla.redhat.com/show_bug.cgi?id=1259958#c1 Would it be possible to have the '--lock-stop' cmd block until the other nodes realize it was indeed stopped? Or have the remove cmd retry some how? Otherwise it's on the user to remember to have patience. # node 1 [root@harding-02 ~]# vgchange --lock-stop vg # node 2 [root@harding-03 ~]# vgremove vg Lockspace for "vg" not stopped on other hosts [root@harding-03 ~]# vgremove vg Lockspace for "vg" not stopped on other hosts [root@harding-03 ~]# vgremove vg Lockspace for "vg" not stopped on other hosts [root@harding-03 ~]# vgremove vg Volume group "vg" successfully removed Version-Release number of selected component (if applicable): 3.10.0-510.el7.x86_64 lvm2-2.02.165-4.el7 BUILT: Thu Sep 22 01:47:19 CDT 2016 lvm2-libs-2.02.165-4.el7 BUILT: Thu Sep 22 01:47:19 CDT 2016 lvm2-cluster-2.02.165-4.el7 BUILT: Thu Sep 22 01:47:19 CDT 2016 device-mapper-1.02.134-4.el7 BUILT: Thu Sep 22 01:47:19 CDT 2016 device-mapper-libs-1.02.134-4.el7 BUILT: Thu Sep 22 01:47:19 CDT 2016 device-mapper-event-1.02.134-4.el7 BUILT: Thu Sep 22 01:47:19 CDT 2016 device-mapper-event-libs-1.02.134-4.el7 BUILT: Thu Sep 22 01:47:19 CDT 2016 device-mapper-persistent-data-0.6.3-1.el7 BUILT: Fri Jul 22 05:29:13 CDT 2016 cmirror-2.02.165-4.el7 BUILT: Thu Sep 22 01:47:19 CDT 2016 sanlock-3.4.0-1.el7 BUILT: Fri Jun 10 11:41:03 CDT 2016 sanlock-lib-3.4.0-1.el7 BUILT: Fri Jun 10 11:41:03 CDT 2016 lvm2-lockd-2.02.165-4.el7 BUILT: Thu Sep 22 01:47:19 CDT 2016
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.