+++ This bug was initially created as a clone of Bug #1400816 +++ Description of problem: In case of 8 Node gluster having 4 node Ganesha cluster on it , symlinks are created on non-ganesha nodes from /etc/ganesha/ganesha.conf to /var/run/gluster/shared_storage/ Version-Release number of selected component (if applicable): glusterfs-ganesha-3.8.4-5.el7rhgs.x86_64 nfs-ganesha-gluster-2.4.1-1.el7rhgs.x86_64 How reproducible: Steps to Reproduce: 1.Create 8 node gluster (Do peer probe to all 8 nodes having gluster packages) 2.Create 4 node cluster and enable ganesha on it #gluster nfs-ganesha enable Actual results: Symlinks from /etc/ganesha/ganesha.conf -> /var/run/gluster/shared_storage/nfs-ganesha/ganesha.conf are created on non-ganesha nodes which are part of 8 node gluster Expected results: Nodes which do not have ganesha enable,On those nodes symlinks should not be created from /etc/ganesha/ganesha.conf -> /var/run/gluster/shared_storage/nfs-ganesha/ganesha.conf --- Additional comment from Manisha Saini on 2016-12-05 08:54:48 EST --- While trying creating ganesha cluster on 4 nodes out of 8 nodes in gluster,then if any of the node does not have ganesha packages,then it fails to enable nfs-ganesha cluster [root@dhcp47-3 ganesha]# gluster nfs-ganesha enable Enabling NFS-Ganesha requires Gluster-NFS to be disabled across the trusted pool. Do you still want to continue? (y/n) y This will take a few minutes to complete. Please wait .. nfs-ganesha: failed: Staging failed on dhcp46-232.lab.eng.blr.redhat.com. Error: creation of symlink ganesha.conf in /etc/ganesha failed dhcp46-232.lab.eng.blr.redhat.com -Node which do not have ganesha packages
REVIEW: http://review.gluster.org/16041 (ganesha/glusterd : create 'ganesha.conf' symlink for nodes in ganesha cluster) posted (#1) for review on master by jiffin tony Thottan (jthottan)
COMMIT: http://review.gluster.org/16041 committed in master by Atin Mukherjee (amukherj) ------ commit 4a11b1d8aa79bb6bd26d2a06b3c4c3a9574329d4 Author: Jiffin Tony Thottan <jthottan> Date: Tue Dec 6 15:53:10 2016 +0530 ganesha/glusterd : create 'ganesha.conf' symlink for nodes in ganesha cluster Change-Id: I27503558da176f0b1a1f0953a7e7ebe86976608d BUG: 1401877 Signed-off-by: Jiffin Tony Thottan <jthottan> Reviewed-on: http://review.gluster.org/16041 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> Reviewed-by: Atin Mukherjee <amukherj>
The above patch only fixes issue for "gluster nfs-ganesha enable" command. Similar change is required for disable as well. SInce this changes moved out of master, I am changing release to 3.10
REVIEW: https://review.gluster.org/17138 (glusterd/ganesha : perform removal of ganesha.conf on nodes only in ganesha cluster) posted (#1) for review on release-3.10 by jiffin tony Thottan (jthottan)
COMMIT: https://review.gluster.org/17138 committed in release-3.10 by Kaleb KEITHLEY (kkeithle) ------ commit eb247da4ef06e6b93c1bbe987ee76176781aa68a Author: Jiffin Tony Thottan <jthottan> Date: Fri Apr 28 17:27:46 2017 +0530 glusterd/ganesha : perform removal of ganesha.conf on nodes only in ganesha cluster Change-Id: I864ecd9391adf80fb1fa6ad2f9891a9ce77135e7 BUG: 1401877 Signed-off-by: Jiffin Tony Thottan <jthottan> Reviewed-on: https://review.gluster.org/17138 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> Reviewed-by: Kaleb KEITHLEY <kkeithle>
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.11.0, please open a new bug report. glusterfs-3.11.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/announce/2017-May/000073.html [2] https://www.gluster.org/pipermail/gluster-users/
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.