Bug 1251857
Summary: | nfs-ganesha: new volume creation tries to bring up glusterfs-nfs even when nfs-ganesha is already on | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Meghana <mmadhusu> | |
Component: | ganesha-nfs | Assignee: | Soumya Koduri <skoduri> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | low | Docs Contact: | ||
Priority: | high | |||
Version: | mainline | CC: | asriram, asrivast, divya, kkeithle, nlevinki, saujain, skoduri, storage-qa-internal, vagarwal | |
Target Milestone: | --- | Keywords: | Reopened | |
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1226817 | |||
: | 1254419 (view as bug list) | Environment: | ||
Last Closed: | 2016-06-16 13:30:14 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: | 1226817 | |||
Bug Blocks: | 1202842, 1216951, 1240614, 1254419 |
Comment 1
Meghana
2015-08-10 07:16:04 UTC
REVIEW: http://review.gluster.org/11871 (Set nfs.disable to "on" when global NFS-Ganesha key is enabled) posted (#1) for review on master by Meghana M (mmadhusu) REVIEW: http://review.gluster.org/11871 (Set nfs.disable to "on" when global NFS-Ganesha key is enabled) posted (#2) for review on master by Meghana M (mmadhusu) REVIEW: http://review.gluster.org/11871 (Set nfs.disable to "on" when global NFS-Ganesha key is enabled) posted (#3) for review on master by Meghana M (mmadhusu) COMMIT: http://review.gluster.org/11871 committed in master by Kaleb KEITHLEY (kkeithle) ------ commit cdf238e7c90273beff73617481d19d77fc8014db Author: Meghana M <mmadhusu> Date: Mon Aug 3 03:03:07 2015 +0530 Set nfs.disable to "on" when global NFS-Ganesha key is enabled "nfs.disable" gets set to "on" for all the existing volumes, when the command "gluster nfs-ganesha enable" is executed. When a new volume is created,it gets exported via Gluster-NFS on the nodes outside the NFS-Ganesha. To fix this, the "nfs.disable" key is set to "on" before starting the volume, whenever the global option is set to "enable". Change-Id: I7ce58928c36eadb8c122cded5bdcea271a0a4ffa BUG: 1251857 Signed-off-by: Meghana M <mmadhusu> Reviewed-on: http://review.gluster.org/11871 Reviewed-by: jiffin tony Thottan <jthottan> Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaleb KEITHLEY <kkeithle> Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well. 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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |