[Bugs] [Bug 1425723] New: nfs-ganesha volume export file remains stale in shared_storage_volume when volume is deleted

bugzilla at redhat.com bugzilla at redhat.com
Wed Feb 22 08:50:32 UTC 2017


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

            Bug ID: 1425723
           Summary: nfs-ganesha volume export file remains stale in
                    shared_storage_volume when volume is deleted
           Product: GlusterFS
           Version: 3.10
         Component: glusterd
          Keywords: Triaged
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: jthottan at redhat.com
                CC: aloganat at redhat.com, amukherj at redhat.com,
                    bugs at gluster.org, jthottan at redhat.com,
                    rhs-bugs at redhat.com, skoduri at redhat.com,
                    storage-qa-internal at redhat.com, vbellur at redhat.com
        Depends On: 1395989
            Blocks: 1351530, 1417147



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

Description of problem:
nfs-ganesha volume export file remains stale in shared_storage_volume when
volume is deleted. 

If the export file is not removed, next time when the volume is created with
same name the older export file is getting honoured.

Version-Release number of selected component (if applicable):
nfs-ganesha-gluster-2.4.1-1.el7rhgs.x86_64
glusterfs-ganesha-3.8.4-5.el7rhgs.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Create nfs-ganehsa cluster and create volume.
2. Set ganesha.enable to on for that volume.
3. Ensure the volume is exported.
4. Stop and delete the volume.

Actual results:
nfs-ganesha volume export file remains stale in shared_storage_volume when
volume is deleted

Expected results:
nfs-ganesha volume export file should get removed when volume is deleted. 

Additional info:


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1395989
[Bug 1395989] nfs-ganesha volume export file remains stale in
shared_storage_volume when volume is deleted
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list