+++ This bug was initially created as a clone of Bug #1382258 +++ +++ 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. --- Additional comment from Worker Ant on 2016-10-06 03:12:37 EDT --- 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) --- Additional comment from Worker Ant on 2016-10-06 03:15:23 EDT --- 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) --- Additional comment from Worker Ant on 2016-10-19 09:55:27 EDT --- 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> --- Additional comment from Shyamsundar on 2017-03-06 12:29:11 EST --- 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/
REVIEW: https://review.gluster.org/17080 (common-ha: Use UpdateExports dbus msg for refresh-config) posted (#1) for review on release-3.10 by jiffin tony Thottan (jthottan)
REVIEW: https://review.gluster.org/17080 (common-ha: Use UpdateExports dbus msg for refresh-config) posted (#2) for review on release-3.10 by jiffin tony Thottan (jthottan)
COMMIT: https://review.gluster.org/17080 committed in release-3.10 by Kaleb KEITHLEY (kkeithle) ------ commit d96ab579478ea3bfea6bacced4407a101cc70866 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. Note : This change was of part of 3.10 branching, but the commit 142ee0c overwrites this patch. Hence resubmitting this change Upstream reference : >Change-Id: Iee7330d33e91db1126974a2ff46becb3764f2e5e >BUG: 1382258 >Author: 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> Change-Id: Iee7330d33e91db1126974a2ff46becb3764f2e5e BUG: 1443478 Author: Soumya Koduri <skoduri> Signed-off-by: Jiffin Tony Thottan <jthottan> Reviewed-on: https://review.gluster.org/17080 Smoke: Gluster Build System <jenkins.org> Reviewed-by: soumya k <skoduri> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org>
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.2, please open a new bug report.