Bug 1426523

Summary:	[GSS] Stale export entries in ganesha.conf after executing "gluster nfs-ganesha disable"
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Riyas Abdulrasak <rnalakka>
Component:	common-ha	Assignee:	Jiffin <jthottan>
Status:	CLOSED ERRATA	QA Contact:	surabhi <sbhaloth>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.2	CC:	amukherj, asoman, asrivast, bmohanra, bugs, jthottan, kkeithle, rhinduja, rhs-bugs, skoduri, storage-qa-internal
Target Milestone:	---	Keywords:	Triaged
Target Release:	RHGS 3.3.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.8.4-24	Doc Type:	Bug Fix
Doc Text:	Stale export entries were not cleaned up correctly from the ganesha.conf file when NFS-Ganesha was disabled; this has now been corrected so that stale export entries are removed.	Story Points:	---
Clone Of:	1425726	Environment:
Last Closed:	2017-09-21 04:33:25 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:	1425726
Bug Blocks:	1417145

Description Riyas Abdulrasak 2017-02-24 06:55:20 UTC

+++ This bug was initially created as a clone of Bug #1425726 +++

Description of problem:
Stale export entries in ganesha.conf in shared storage after executing "gluster nfs-ganesha disable"

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

glusterfs-3.8.4-14


How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
stale entries in ganesha.conf

Expected results:
entries should be removed

Additional info:

--- Additional comment from Worker Ant on 2017-02-22 04:07:54 EST ---

REVIEW: https://review.gluster.org/16708 (ganesha/scripts : Remove export entries from ganesha.conf during cleanup) posted (#1) for review on release-3.10 by jiffin tony Thottan (jthottan)

Comment 6 surabhi 2017-05-04 13:07:24 UTC

Verified as follows:

Execute gluster nfs-ganesha disable and check the /etc/ganesha/ganesha.conf file for any stale export entries.

Verified that there are no stale export entries in ganesha.conf and then gluster nfs-ganesha enable works fine.

Version:

nfs-ganesha-2.4.4-4.el7rhgs.x86_64
glusterfs-ganesha-3.8.4-24.el7rhgs.x86_64
nfs-ganesha-gluster-2.4.4-4.el7rhgs.x86_64


Moving the BZ verified.

Comment 8 Jiffin 2017-08-24 09:33:16 UTC

Looks good to me

Comment 10 errata-xmlrpc 2017-09-21 04:33:25 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2774

Comment 11 errata-xmlrpc 2017-09-21 04:57:48 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2774