[Bugs] [Bug 1463191] New: gfapi: discard glfs object when volume is deleted

[bugzilla at redhat.com]

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

            Bug ID: 1463191
           Summary: gfapi: discard glfs object when volume is deleted
           Product: GlusterFS
           Version: mainline
         Component: libgfapi
          Assignee: bugs at gluster.org
          Reporter: prasanna.kalever at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org



Description of problem:

currently, once we have a glfs object in hand for a given volume, after
deleting and recreating the volume with same name, we still can access new
volume using the old glfs object, which is wrong.

Version-Release number of selected component (if applicable):
mainline

How reproducible:
1. write a gfapi program, once you are done calling glfs_init() try creating a
file in the volume, now apply break-point there.

2. delete the volume and recreate the volume with the same name.

3. now continue with your program, in the next lines try creating another file
in the volume using the same old glfs object

4. surprisingly it allows to create.

My use-case was more like calling glfs_get_volumeid() returns old volume id
rather than throwing an error which should say glfs object is not valid or
worst case return new volume id, but in my case it returned old uuid.

Refer https://bugzilla.redhat.com/show_bug.cgi?id=1461808#c9 for some more
interesting context and sample programs.


Actual results:
with old glfs object we still can access new volume

Expected results:
return invalid object.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.