Bug 1260505

Summary:	RFE : cli improvements for ganesha
Product:	[Community] GlusterFS	Reporter:	Jiffin <jthottan>
Component:	ganesha-nfs	Assignee:	bugs <bugs>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	high	Docs Contact:
Priority:	urgent
Version:	mainline	CC:	amukherj, bugs, jthottan, kkeithle, ndevos, skoduri, vbellur
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-19 05:20:23 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:
Bug Depends On:	1260509, 1261444
Bug Blocks:

Description Jiffin 2015-09-07 06:27:10 UTC

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Atin Mukherjee 2017-01-25 08:38:07 UTC

The bug description has no details here, what are we supposed to enhance? I am assigning this to nfs-ganesha component for further details and actions.

Comment 2 Jiffin 2017-01-25 09:58:11 UTC

AFAIR  I filed this bug to introduce force option for ganesha cli's. If somehow the option "nfs-ganesha" or vol set option "ganesha.enable" are inconsistent across the cluster, then there is no way come out of that state via cli. By introducing "force", the existing inconsistency can over writte.

Comment 3 Vijay Bellur 2018-11-19 05:40:01 UTC

Migrated to github:

https://github.com/gluster/glusterfs/issues/568

Please follow the github issue for further updates on this bug.