Red Hat Bugzilla – Bug 1347922
nfs-ganesha disable doesn't delete nfs-ganesha folder from /var/run/gluster/shared_storage
Last modified: 2017-03-23 01:37:24 EDT
Description of problem: nfs-ganesha disable doesn't delete nfs-ganesha folder from /var/run/gluster/shared_storage Version-Release number of selected component (if applicable): nfs-ganesha-2.3.1-8 How reproducible: Always Steps to Reproduce: 1. On a already running nfs-ganesha cluster, disable nfs-ganesha using below command: gluster nfs-ganesha disable 2. Observe that the nfs-ganesha folder, which is being created under /var/run/gluster/shared_storage during nfs-ganesha enable, doesn't get deleted from the path Actual results: nfs-ganesha disable doesn't delete nfs-ganesha folder from /var/run/gluster/shared_storage Expected results: the nfs-ganesha folder should get deleted from /var/run/gluster/shared_storage once we disable nfs-ganesha on the cluster. Additional info:
Patch http://review.gluster.org/#/c/14833/ got merged in upstream 3.8
This change is already part of rebase
With current design in 3.2, once we disable nfs-ganesha on the cluster, the nfs-ganesha folder under /var/run/gluster/shared_storage should not get deleted because we are recommending to manually create it once we setup ganesha for the first time. So after tearing down ganesha cluster, following is the behavior: symlink to ganesha.conf under shared storage will get removed [root@dhcp43-110 ~]# cd /etc/ganesha/ [root@dhcp43-110 ganesha]# ls ganesha.conf ganesha-ha.conf ganesha-ha.conf.sample and the nfs-ganesha folder under shared storage will still be there but entries other than ganesha.conf and ganesha-ha.conf will get removed: [root@dhcp43-110 ganesha]# cd /var/run/gluster/shared_storage/ [root@dhcp43-110 shared_storage]# ls nfs-ganesha [root@dhcp43-110 shared_storage]# cd nfs-ganesha/ [root@dhcp43-110 nfs-ganesha]# ls ganesha.conf ganesha-ha.conf Jiffin, Please confirm that the above behavior is as expected. Based on that i will mark this bug as Verified.
Correct Shashank. This is current behavior. Previously directory "nfs-ganesha" in shared storage was used only for storing state of different nfs client. Now it is stored to store configuration file like ganesha.conf and ganesha-ha.conf. So all the entries expect these two should be deleted from "nfs-ganesha" folder in shared storage.
Based on comment 7 and 8, 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