Description of problem: If a user set `gluster nfs-ganesha enable` and if commits failed on one of the nodes(i.e /va/lib/glusterd/options is not updated), then it will cause a dead lock for the option `gluster nfs-ganesha` bith disable/enable will be prevented from the cli saying it is already enable/ disabled in one of the nodes. Version-Release number of selected component (if applicable): mainline Additional info: It will be better to have force option which can override the deadlock
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.