REVIEW: http://review.gluster.org/11477 (NFS-Ganesha : Unexport fails after S31ganesha-start script is run) posted (#3) for review on master by Meghana M (mmadhusu)

REVIEW: http://review.gluster.org/11477 (NFS-Ganesha : Unexport fails after S31ganesha-start script is run) posted (#4) for review on master by Meghana M (mmadhusu)

REVIEW: http://review.gluster.org/11477 (NFS-Ganesha : Unexport fails after S31ganesha-start script is run) posted (#5) for review on master by Meghana M (mmadhusu)

REVIEW: http://review.gluster.org/11477 (NFS-Ganesha : Unexport fails after S31ganesha-start script is run) posted (#6) for review on master by Meghana M (mmadhusu)

REVIEW: http://review.gluster.org/11477 (NFS-Ganesha : Unexport fails after S31ganesha-start script is run) posted (#7) for review on master by Meghana M (mmadhusu)

REVIEW: http://review.gluster.org/11477 (NFS-Ganesha : Unexport fails after S31ganesha-start script is run) posted (#8) for review on master by Meghana M (mmadhusu)

COMMIT: http://review.gluster.org/11477 committed in master by Kaleb KEITHLEY (kkeithle) 
------
commit 8def0f28c908224359a04ec2f658a3ba241c7249
Author: Meghana M <mmadhusu>
Date:   Tue Jun 30 23:47:39 2015 +0530

    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: Ibf639eb3556b1e51dd8dcb0c784a6a7f07badb97
    BUG: 1238054
    Signed-off-by: Meghana M <mmadhusu>
    Reviewed-on: http://review.gluster.org/11477
    Reviewed-by: Niels de Vos <ndevos>
    Reviewed-by: Kaleb KEITHLEY <kkeithle>
    Tested-by: Gluster Build System <jenkins.com>

Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.

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.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user