[Bugs] [Bug 1403144] New: [GANESHA] Unable to export the ganesha volume after doing volume start and stop

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1403144

            Bug ID: 1403144
           Summary: [GANESHA]Unable to export the ganesha volume after
                    doing volume start and stop
           Product: GlusterFS
           Version: 3.9
         Component: glusterd
          Keywords: Triaged
          Priority: urgent
          Assignee: bugs at gluster.org
          Reporter: jthottan at redhat.com
                CC: bugs at gluster.org, jthottan at redhat.com,
                    kkeithle at redhat.com, msaini at redhat.com,
                    ndevos at redhat.com, rhs-bugs at redhat.com,
                    skoduri at redhat.com, storage-qa-internal at redhat.com
        Depends On: 1401806, 1401822



+++ This bug was initially created as a clone of Bug #1401822 +++

+++ This bug was initially created as a clone of Bug #1401806 +++

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:

--- Additional comment from Worker Ant on 2016-12-06 03:13:49 EST ---

REVIEW: http://review.gluster.org/16037 (ganesha/scripts : find export id for
already exported volume in S31ganesha-start.sh) posted (#1) for review on
master by jiffin tony Thottan (jthottan at redhat.com)

--- Additional comment from Worker Ant on 2016-12-08 11:49:37 EST ---

COMMIT: http://review.gluster.org/16037 committed in master by Kaleb KEITHLEY
(kkeithle at redhat.com) 
------
commit 58a58e706da73ee751b7cd98c23e6675667fefdb
Author: Jiffin Tony Thottan <jthottan at redhat.com>
Date:   Tue Dec 6 13:38:21 2016 +0530

    ganesha/scripts : find export id for already exported volume in
S31ganesha-start.sh

    Change-Id: Iada90ed215966d3f526fa20aa5359b67f25a6944
    BUG: 1401822
    Signed-off-by: Jiffin Tony Thottan <jthottan at redhat.com>
    Reviewed-on: http://review.gluster.org/16037
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: soumya k <skoduri at redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle at redhat.com>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1401806
[Bug 1401806] [GANESHA] Volume restart(stop followed by start) does not
reexporting the volume
https://bugzilla.redhat.com/show_bug.cgi?id=1401822
[Bug 1401822] [GANESHA]Unable to export the ganesha volume after doing
volume start and stop
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.