Description of problem: After doing start and stop on volume having ganesha enable,volume is failed to export again Version-Release number of selected component (if applicable): # rpm -qa | grep ganesha nfs-ganesha-2.4.1-2.el7rhgs.x86_64 glusterfs-ganesha-3.8.4-7.el7rhgs.x86_64 nfs-ganesha-gluster-2.4.1-2.el7rhgs.x86_64 How reproducible: Steps to Reproduce: 1.Create 4 node ganesha cluster on 8 node gluster and enable ganesha on it 2.Create a volume and enable ganesha 3.Check showmount -e.Volume is exported 4.Stop the volume 5.Again start the same volunme Actual results: on restart of the volume,volume failed to get exported again. Observed the following messages in ganesha.log 06/12/2016 12:07:24 : epoch 08220000 : dhcp47-3.lab.eng.blr.redhat.com : ganesha.nfsd-10937[dbus_heartbeat] glusterfs_create_export :FSAL :EVENT :Volume ganeshaVol1 exported at : '/' 06/12/2016 12:09:12 : epoch 08220000 : dhcp47-3.lab.eng.blr.redhat.com : ganesha.nfsd-10937[dbus_heartbeat] gsh_export_addexport :EXPORT :CRIT :Error finding exports: EXPORT(Export_Id=) because No such file or directory 06/12/2016 12:09:12 : epoch 08220000 : dhcp47-3.lab.eng.blr.redhat.com : ganesha.nfsd-10937[dbus_heartbeat] dbus_message_entrypoint :DBUS :MAJ :Method (AddExport) on (org.ganesha.nfsd.exportmgr) failed: name = (org.freedesktop.DBus.Error.InvalidArgs), message = (Error finding exports: EXPORT(Export_Id=) because No such file or directory) Expected results: Volume should be exported successfully on restart of the volume Additional info:
Created attachment 1228305 [details] new_S31ganesha-start The workaround for above issue is attached to the bug. Please copy this file to /var/lib/glusterd/hooks/1/start/post/ for testing purpose
Patch posted upstream for review : http://review.gluster.org/#/c/16037/1
upstream mainline : http://review.gluster.org/16037 upstream 3.9 : http://review.gluster.org/16093 downstream patch :https://code.engineering.redhat.com/gerrit/#/c/92556/
Verified this Bug on [root@dhcp47-3 tmp]# rpm -qa | grep ganesha nfs-ganesha-2.4.1-2.el7rhgs.x86_64 glusterfs-ganesha-3.8.4-8.el7rhgs.x86_64 nfs-ganesha-gluster-2.4.1-2.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