[Bugs] [Bug 1568674] [shared-storage-vol]: Dead lock between disable and enable of shared volume blaming itself
bugzilla at redhat.com
bugzilla at redhat.com
Thu Jul 18 07:48:34 UTC 2019
https://bugzilla.redhat.com/show_bug.cgi?id=1568674
Sanju <srakonde at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |WONTFIX
Last Closed| |2019-07-18 07:48:34
--- Comment #2 from Sanju <srakonde at redhat.com> ---
Description of problem:
=======================
Consider a entry scenario where shared volume is enabled and mounted on all
nodes of trusted servers. Now if any glusterd is down and shared volume is
disabled, it returns success and any subsequent enable/disable blame it
exists/non-exist respectively.
[root at dhcp41-226 ~]# gluster volume set all cluster.enable-shared-storage
enable
volume set: failed: Shared storage volume(gluster_shared_storage) already
exists.
[root at dhcp41-226 ~]# gluster volume set all cluster.enable-shared-storage
disable
Disabling cluster.enable-shared-storage will delete the shared storage
volume(gluster_shared_storage), which is used by snapshot scheduler,
geo-replication and NFS-Ganesha. Do you still want to continue? (y/n) y
volume set: failed: Shared storage volume does not exist. Please enable shared
storage for creating shared storage volume.
[root at dhcp41-226 ~]# gluster volume set all cluster.enable-shared-storage
enable
volume set: failed: Shared storage volume(gluster_shared_storage) already
exists.
[root at dhcp41-226 ~]# gluster volume set all cluster.enable-shared-storage
disable
Disabling cluster.enable-shared-storage will delete the shared storage
volume(gluster_shared_storage), which is used by snapshot scheduler,
geo-replication and NFS-Ganesha. Do you still want to continue? (y/n) y
volume set: failed: Shared storage volume does not exist. Please enable shared
storage for creating shared storage volume.
[root at dhcp41-226 ~]#
No force option is available to come out of this dead loop. volume Stop/Start
force also did not help.
Workaround:
[root at dhcp41-226 ~]# gluster volume stop gluster_shared_storage force
Stopping the shared storage volume(gluster_shared_storage), will affect
features like snapshot scheduler, geo-replication and NFS-Ganesha. Do you still
want to continue? (y/n) y
volume stop: gluster_shared_storage: success
[root at dhcp41-226 ~]# gluster volume delete gluster_shared_storage
Deleting the shared storage volume(gluster_shared_storage), will affect
features like snapshot scheduler, geo-replication and NFS-Ganesha. Do you still
want to continue? (y/n) y
volume delete: gluster_shared_storage: success
[root at dhcp41-226 ~]# gluster volume set all cluster.enable-shared-storage
enable
volume set: success
[root at dhcp41-226 ~]#
at https://review.gluster.org/19897 we have decided to not fix this issue as it
is breaking some existing functionalities. So, I'm closing this bug as won't
fix.
Thanks,
Sanju
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Bugs
mailing list