Bug 1382258

Summary:	RFE: Support to update NFS-Ganesha export options dynamically
Product:	[Community] GlusterFS	Reporter:	Soumya Koduri <skoduri>
Component:	common-ha	Assignee:	Soumya Koduri <skoduri>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, bugs, jthottan, kkeithle, mzywusko, ndevos, rhs-bugs, storage-qa-internal
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-3.10.0	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1370027
Clones:	1443478 (view as bug list)		Environment:
Last Closed:	2017-03-06 17:29:11 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:
Bug Blocks:	1370027, 1443478

Description Soumya Koduri 2016-10-06 07:11:02 UTC

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

Description of problem:

Like many other NFS servers, NFS-Ganesha also should be able to dynamically configure and update export options (like Access Protocols, Client Permissions etc) of an already exported share. The work-around used till now was to unexport and re-export the share with the new options configured. But with upstream NFS-Ganesha 2.4 release we now have that support. This bug is to track those changes and get the required testing done.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Red Hat Bugzilla Rules Engine on 2016-08-25 02:03:50 EDT ---

This bug is automatically being proposed for the current release of Red Hat Gluster Storage 3 under active development, by setting the release flag 'rhgs‑3.2.0' to '?'. 

If this bug should be proposed for a different release, please manually change the proposed release flag.

--- Additional comment from Soumya Koduri on 2016-08-25 08:11:55 EDT ---

For our RHGS NFS-Ganesha clustered soluction, we need to make changes in 'refresh-config' functionality to use the new Dbus event provided to update exports dynamically.

Comment 1 Worker Ant 2016-10-06 07:12:37 UTC

REVIEW: http://review.gluster.org/15617 (common-ha: Use UpdateExports dbus msg for refresh-config) posted (#1) for review on master by soumya k (skoduri)

Comment 2 Worker Ant 2016-10-06 07:15:23 UTC

REVIEW: http://review.gluster.org/15617 (common-ha: Use UpdateExports dbus msg for refresh-config) posted (#2) for review on master by soumya k (skoduri)

Comment 3 Worker Ant 2016-10-19 13:55:27 UTC

COMMIT: http://review.gluster.org/15617 committed in master by Kaleb KEITHLEY (kkeithle) 
------
commit 20d2b36f3acc2f27527b7913d2ad939848395aeb
Author: Soumya Koduri <skoduri>
Date:   Mon Oct 3 12:35:39 2016 +0530

    common-ha: Use UpdateExports dbus msg for refresh-config
    
    In nfs-ganesha 2.4, new dbs msg type "UpdateExports" support
    has been added. With this support, the exports can be re-configured
    dynamically without the need to re-export the entries.
    
    Change-Id: Iee7330d33e91db1126974a2ff46becb3764f2e5e
    BUG: 1382258
    Signed-off-by: Soumya Koduri <skoduri>
    Reviewed-on: http://review.gluster.org/15617
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle>

Comment 4 Shyamsundar 2017-03-06 17:29:11 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.0, please open a new bug report.

glusterfs-3.10.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/gluster-users/2017-February/030119.html
[2] https://www.gluster.org/pipermail/gluster-users/