Bug 1231211

Summary:	cli : deadlock in global option nfs-ganesha
Product:	[Community] GlusterFS	Reporter:	Jiffin <jthottan>
Component:	cli	Assignee:	Jiffin <jthottan>
Status:	CLOSED EOL	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.7.1	CC:	bugs, jthottan
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-08 10:58:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jiffin 2015-06-12 11:52:39 UTC

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

Comment 2 Kaushal 2017-03-08 10:58:00 UTC

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.