Bug 1351151 - ganesha.enable remains on in volume info file even after we disable nfs-ganesha on the cluster.
Summary: ganesha.enable remains on in volume info file even after we disable nfs-ganes...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: ganesha-nfs
Version: 3.8.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jiffin
QA Contact:
URL:
Whiteboard:
Depends On: 1347923 1349270
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-29 11:17 UTC by Jiffin
Modified: 2016-07-08 14:42 UTC (History)
9 users (show)

Fixed In Version: glusterfs-3.8.1
Clone Of: 1349270
Environment:
Last Closed: 2016-07-08 14:42:55 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Comment 1 Vijay Bellur 2016-06-29 11:17:42 UTC 
REVIEW: http://review.gluster.org/14831 (glusterd/ganesha : persist value set by teardown in info file) posted (#1) for review on release-3.8 by jiffin tony Thottan (jthottan)
Comment 2 Vijay Bellur 2016-07-04 05:39:26 UTC 
COMMIT: http://review.gluster.org/14831 committed in release-3.8 by Atin Mukherjee (amukherj) 
------
commit 3541810cdf6bc3914c4f7531500bc0ae32954f84
Author: Jiffin Tony Thottan <jthottan>
Date:   Thu Jun 23 11:56:10 2016 +0530

    glusterd/ganesha : persist value set by teardown in info file
    
    During teardown, all the volumes exported via NFS-Ganesha will be
    unexported. So all related volume options need to reset. Currently
    this change made using dict_set on volopt dictionary, i.e change
    is only reflected in memory not persisted in the volume info file
    Therefore incase of glusterd restart this data can be lost.
    
    Also this patch fix similar issue in ganesha_manage_export().
    
    Upstream reference :
    >Change-Id: Ib843ac30adb28a70e13a9a1df57020ef2f3db8a4
    >BUG: 1349270
    >Signed-off-by: Jiffin Tony Thottan <jthottan>
    >Reviewed-on: http://review.gluster.org/14778
    >Smoke: Gluster Build System <jenkins.org>
    >NetBSD-regression: NetBSD Build System <jenkins.org>
    >CentOS-regression: Gluster Build System <jenkins.org>
    >Reviewed-by: Kaleb KEITHLEY <kkeithle>
    >Reviewed-by: Atin Mukherjee <amukherj>
    >(cherry picked from commit 16c34b101f604a09a5c735fb39815c59ee4ecbdb)
    
    Change-Id: Ib843ac30adb28a70e13a9a1df57020ef2f3db8a4
    BUG: 1351151
    Signed-off-by: Jiffin Tony Thottan <jthottan>
    Reviewed-on: http://review.gluster.org/14831
    Reviewed-by: Atin Mukherjee <amukherj>
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
Comment 3 Niels de Vos 2016-07-08 14:42:55 UTC 
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.1, please open a new bug report.

glusterfs-3.8.1 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://thread.gmane.org/gmane.comp.file-systems.gluster.packaging/156
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
Note You need to log in before you can comment on or make changes to this bug.