Red Hat Bugzilla – Bug 1251857
nfs-ganesha: new volume creation tries to bring up glusterfs-nfs even when nfs-ganesha is already on
Last modified: 2016-06-16 09:30:14 EDT
Once we have nfs-ganesha up and running, the new volume creation still tries to bring up the glusterfs-nfs up, though unsuccessfully.
This is visible once you check the gluster status for that particular newly created volume,
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a volume of type 6x2, start it
2. bring up nfs-ganesha, after doing all the pre-requisites
3. create another volume of any type,
4. gluster volume status <name of newly created volume>
step 4 results in response as displayed in description section
we should have a mechanism to find out if nfs-ganesha is already running, then the new volume should accept that as the nfs server, rather try to bring glusterfs-nfs.
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 (email@example.com)
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 (firstname.lastname@example.org)
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 (email@example.com)
COMMIT: http://review.gluster.org/11871 committed in master by Kaleb KEITHLEY (firstname.lastname@example.org)
Author: Meghana M <email@example.com>
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".
Signed-off-by: Meghana M <firstname.lastname@example.org>
Reviewed-by: jiffin tony Thottan <email@example.com>
Tested-by: NetBSD Build System <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Kaleb KEITHLEY <firstname.lastname@example.org>
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.