Description of problem: When the node is deleted from existing ganesha cluster,volume entry of the exported volume gets deleted from /etc/ganesha/ganesha.conf file. As a result the existing node reflects the stale entry of the volume in showmount -e localhost Version-Release number of selected component (if applicable): # rpm -qa | grep ganesha nfs-ganesha-2.4.1-3.el7rhgs.x86_64 nfs-ganesha-gluster-2.4.1-3.el7rhgs.x86_64 glusterfs-ganesha-3.8.4-9.el7rhgs.x86_64 How reproducible: Consistently Steps to Reproduce: 1.Create 6 node ganesha cluster on 8 node gluster.Enable ganesha on it 2.Delete 1 node from existing ganesha cluster /usr/libexec/ganesha/ganesha-ha.sh --delete /var/run/gluster/shared_storage/nfs-ganesha/ dhcp46-232.lab.eng.blr.redhat.com 3.Check /etc/ganesha/ganesha.conf file. Actual results: Check /etc/ganesha/ganesha.conf file.Volume which was previously exported gets deleted from this file. showmount -e localhost reflects stale entry of previously exported volume In this case if the node is deleted and again added,previously exported volume (before node delete) is not exported on the node which is added. Expected results: It should not modify the /etc/ganesha/ganesha.conf file. Volume should be exported on the newly added node Additional info:
upstream mainline patch http://review.gluster.org/#/c/16209/ posted for review.
downstream patch : https://code.engineering.redhat.com/gerrit/#/c/93568/
Verified this Bug on # rpm -qa | grep ganesha glusterfs-ganesha-3.8.4-10.el7rhgs.x86_64 nfs-ganesha-gluster-2.4.1-3.el7rhgs.x86_64 nfs-ganesha-2.4.1-3.el7rhgs.x86_64 As the issue is no more observed,Hence marking this Bug as verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2017-0486.html