+++ This bug was initially created as a clone of Bug #1389746 +++
+++ This bug was initially created as a clone of Bug #1389661 +++
Description of problem:
Refresh config failed while exporting subdirectories within a volume.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a ganesha cluster, create a volume and enable nfs-ganesha on that volume.
2. Mount the volume and create subdirectories.
3. Edit the export.conf file to export subdirectories within the volume.
conf file path: /var/run/gluster/shared_storage/nfs-ganesha/exports/export.testvol1.conf
4. Run refresh config.
/usr/libexec/ganesha/ganesha-ha.sh --refresh-config /var/run/gluster/shared_storage/nfs-ganesha/ testvol1
Refresh config failed.
Refresh config should succeed and subdirectory should be exported.
Edited export.conf file:
Export_Id = 2;
Path = "/testvol1/user2/dir0";
name = GLUSTER;
Access_type = RW;
Disable_ACL = true;
Protocols = "3", "4" ;
Transports = "UDP","TCP";
SecType = "sys";
Error message in command prompt:
[root@dhcp47-155 ~]# /usr/libexec/ganesha/ganesha-ha.sh --refresh-config /var/run/gluster/shared_storage/nfs-ganesha/ testvol1
Error: refresh-config failed on dhcp46-101.
ganesha.log log snippet:
28/10/2016 11:36:09 : epoch 40270000 : dhcp46-101.lab.eng.blr.redhat.com : ganesha.nfsd-22434[dbus_heartbeat] dbus_message_entrypoint :DBUS :MAJ :Method (RemoveExport) on (org.ganesha.nfsd.exportmgr) failed: name = (org.freedesktop.DBus.Error.InvalidArgs), message = (lookup_export failed with Export id not found)
REVIEW: http://review.gluster.org/16194 (ganesha/scripts : use export id for dbus signals) posted (#1) for review on release-3.7 by jiffin tony Thottan (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/16194 committed in release-3.7 by Kaleb KEITHLEY (email@example.com)
Author: Jiffin Tony Thottan <firstname.lastname@example.org>
Date: Fri Oct 28 17:37:39 2016 +0530
ganesha/scripts : use export id for dbus signals
Currently for add export and update export parameter passed for executing those signal
is "PATH". This is based on assumption that volume name and PATH will always be same.
But it is wrong for subdir exports. The only reliable parameter in export configuration
file is "Export_Id".
Upstream reference :
>Signed-off-by: Jiffin Tony Thottan <email@example.com>
>Smoke: Gluster Build System <firstname.lastname@example.org>
>NetBSD-regression: NetBSD Build System <email@example.com>
>CentOS-regression: Gluster Build System <firstname.lastname@example.org>
>Reviewed-by: soumya k <email@example.com>
>Reviewed-by: Kaleb KEITHLEY <firstname.lastname@example.org>
Signed-off-by: Jiffin Tony Thottan <email@example.com>
Smoke: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: soumya k <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
NetBSD-regression: NetBSD Build System <email@example.com>
Reviewed-by: Kaleb KEITHLEY <firstname.lastname@example.org>
(cherry picked from commit beace6aed3ef27e1e55a420d606ecdfbd56b32b2)
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.7.19, please open a new bug report.
glusterfs-3.7.19 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.