Bug 1405955
| Summary: | NFS-Ganesha:Volume reset for any option causes reset of ganesha enable option and bring down the ganesha services | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Jiffin <jthottan> |
| Component: | glusterd | Assignee: | Jiffin <jthottan> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.7.18 | CC: | amukherj, bugs, jthottan, kkeithle, rhinduja, rhs-bugs, sbhaloth, skoduri, storage-qa-internal |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.7.19 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1405951 | Environment: | |
| Last Closed: | 2017-01-18 13:39:24 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: | 1397450, 1397795, 1402366, 1405951 | ||
| Bug Blocks: | |||
|
Description
Jiffin
2016-12-19 09:53:00 UTC
REVIEW: http://review.gluster.org/16199 (glusterd/ganesha : handle volume reset properly for ganesha options) posted (#1) for review on release-3.7 by jiffin tony Thottan (jthottan) COMMIT: http://review.gluster.org/16199 committed in release-3.7 by Kaleb KEITHLEY (kkeithle) ------ commit 463f06e450798991080d98c6b0fbf195d7e70c93 Author: Jiffin Tony Thottan <jthottan> Date: Wed Nov 23 16:04:26 2016 +0530 glusterd/ganesha : handle volume reset properly for ganesha options The "gluster volume reset" should first unexport the volume and then delete export configuration file. Also reset option is not applicable for ganesha.enable if volume value is "all". This patch also changes the name of create_export_config into manange_export_config Upstream reference : >Change-Id: Ie81a49e7d3e39a88bca9fbae5002bfda5cab34af >BUG: 1397795 >Signed-off-by: Jiffin Tony Thottan <jthottan> >Reviewed-on: http://review.gluster.org/15914 >Smoke: Gluster Build System <jenkins.org> >NetBSD-regression: NetBSD Build System <jenkins.org> >CentOS-regression: Gluster Build System <jenkins.org> >Reviewed-by: soumya k <skoduri> >Reviewed-by: Kaleb KEITHLEY <kkeithle> >Signed-off-by: Jiffin Tony Thottan <jthottan> Change-Id: Ie81a49e7d3e39a88bca9fbae5002bfda5cab34af BUG: 1405955 Signed-off-by: Jiffin Tony Thottan <jthottan> Reviewed-on: http://review.gluster.org/16054 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Kaleb KEITHLEY <kkeithle> Signed-off-by: Jiffin Tony Thottan <jthottan> Reviewed-on: http://review.gluster.org/16199 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.7.19, please open a new bug report. glusterfs-3.7.19 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] https://lists.gluster.org/pipermail/gluster-users/2017-January/029623.html [2] https://www.gluster.org/pipermail/gluster-users/ |