From 04350600eb6255e23e087a3a1d3d15431efc7c6c Mon Sep 17 00:00:00 2001 From: "Kaleb S. KEITHLEY" Date: Thu, 2 Jul 2015 10:22:03 -0400 Subject: NFS-Ganesha : Unexport fails after S31ganesha-start script is run The dbus-send script extracts the export ID from the export config file. It expects the export ID to be written in a particular format. The post-phase hook-script created the export file in a different format, and the dbus-send never gets the correct export ID because of this. Fixing the issue by replacing the write_conf function in the S31ganesha-start hook-script. Also, NFS-Ganesha service stops when dbus signal is sent more than once on the same export. Consecutive start/stop operations creates problems. Fixing all the issues at once. Change-Id: I1306c68e2bc9abd91be1b7f1558c93060cc9c98d BUG: 1238752 Signed-off-by: Kaleb S. KEITHLEY Reviewed-on: http://review.gluster.org/11511 --- extras/ganesha/scripts/create-export-ganesha.sh | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'extras/ganesha/scripts') diff --git a/extras/ganesha/scripts/create-export-ganesha.sh b/extras/ganesha/scripts/create-export-ganesha.sh index 9762c0d110d..668f357409b 100755 --- a/extras/ganesha/scripts/create-export-ganesha.sh +++ b/extras/ganesha/scripts/create-export-ganesha.sh @@ -32,8 +32,7 @@ function write_conf() { echo -e "# WARNING : Using Gluster CLI will overwrite manual # changes made to this file. To avoid it, edit the -# file, copy it over to all the NFS-Ganesha nodes -# and run ganesha-ha.sh --refresh-config." +# file and run ganesha-ha.sh --refresh-config." echo "EXPORT{" echo " Export_Id = 2;" -- cgit