[Bugs] [Bug 1225551] New: [Backup]: Glusterfind session entry persists even after volume is deleted

[bugzilla at redhat.com]

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

            Bug ID: 1225551
           Summary: [Backup]: Glusterfind session entry persists even
                    after volume is deleted
           Product: GlusterFS
           Version: 3.7.0
         Component: glusterfind
          Severity: medium
          Priority: low
          Assignee: bugs at gluster.org
          Reporter: avishwan at redhat.com
        QA Contact: bugs at gluster.org
                CC: avishwan at redhat.com, bugs at gluster.org,
                    khiremat at redhat.com, sanandpa at redhat.com
        Depends On: 1224064, 1225465
            Blocks: 1223636, 1224880



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

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

Description of problem:
When a volume is created and a corresponding glusterfind session, glusterfind
list displays the entry of the session name and volume name. After deletion of
the volume, the session entry should get removed from the display output of
glusterfind list. Glusterfind list should always have only the list of active
glusterfind sessions that are present in that cluster.


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


How reproducible:
Always


Additional info:


[root at dhcp43-140 ~]# 
[root at dhcp43-140 ~]# gluster v info

Volume Name: nash
Type: Distributed-Replicate
Volume ID: ef2333ce-e513-43df-8306-fec77cc479b4
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: 10.70.43.140:/rhs/thinbrick1/nash/dd
Brick2: 10.70.42.75:/rhs/thinbrick1/dd
Brick3: 10.70.43.140:/rhs/thinbrick2/nash/dd
Brick4: 10.70.42.75:/rhs/thinbrick2/dd
Options Reconfigured:
performance.readdir-ahead: on

Volume Name: vol1
Type: Distributed-Replicate
Volume ID: 44f06391-1635-4897-98c2-848e5ae92640
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: 10.70.43.140:/rhs/brick1/dd
Brick2: 10.70.42.75:/rhs/brick1/dd
Brick3: 10.70.43.140:/rhs/brick2/dd
Brick4: 10.70.42.75:/rhs/brick2/dd
Options Reconfigured:
changelog.changelog: on
storage.build-pgfid: on
performance.readdir-ahead: on
[root at dhcp43-140 ~]# 
[root at dhcp43-140 ~]# 
[root at dhcp43-140 ~]# glusterfind list
SESSION                   VOLUME                    SESSION TIME             
---------------------------------------------------------------------------
svol1                     vol1                      2015-05-22 17:02:01      
snash                     nash                      2015-05-22 17:02:58      
sess1                     ozone                     Session Corrupted        
[root at dhcp43-140 ~]# 
[root at dhcp43-140 ~]# 
[root at dhcp43-140 ~]# 
[root at dhcp43-140 ~]# gluster v stop nash
Stopping volume will make its data inaccessible. Do you want to continue? (y/n)
y
volume stop: nash: success
[root at dhcp43-140 ~]# gluster v delete nash
Deleting volume will erase all information about the volume. Do you want to
continue? (y/n) y
volume delete: nash: success
[root at dhcp43-140 ~]# 
[root at dhcp43-140 ~]# gluster v info

Volume Name: vol1
Type: Distributed-Replicate
Volume ID: 44f06391-1635-4897-98c2-848e5ae92640
Status: Stopped
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: 10.70.43.140:/rhs/brick1/dd
Brick2: 10.70.42.75:/rhs/brick1/dd
Brick3: 10.70.43.140:/rhs/brick2/dd
Brick4: 10.70.42.75:/rhs/brick2/dd
Options Reconfigured:
changelog.changelog: on
storage.build-pgfid: on
performance.readdir-ahead: on
[root at dhcp43-140 ~]# 
[root at dhcp43-140 ~]# glusterfind list
SESSION                   VOLUME                    SESSION TIME             
---------------------------------------------------------------------------
svol1                     vol1                      2015-05-22 17:02:01      
snash                     nash                      2015-05-22 17:02:58      
sess1                     ozone                     Session Corrupted        
[root at dhcp43-140 ~]# 
[root at dhcp43-140 ~]# 

[root at dhcp43-140 ~]#


--- Additional comment from Aravinda VK on 2015-05-27 04:02:07 EDT ---

glusterfind is a independent tool which does not know when volume is deleted.
We need to run `glusterfind delete` command before volume delete.

--- Additional comment from Anand Avati on 2015-05-27 08:59:10 EDT ---

REVIEW: http://review.gluster.org/10944 (tools/glusterfind: Cleanup glusterfind
dir after a volume delete) posted (#1) for review on master by Aravinda VK
(avishwan at redhat.com)


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1223636
[Bug 1223636] 3.1 QE Tracker
https://bugzilla.redhat.com/show_bug.cgi?id=1224064
[Bug 1224064] [Backup]: Glusterfind session entry persists even after
volume is deleted
https://bugzilla.redhat.com/show_bug.cgi?id=1224880
[Bug 1224880] [Backup]: Unable to delete session entry from glusterfind
list
https://bugzilla.redhat.com/show_bug.cgi?id=1225465
[Bug 1225465] [Backup]: Glusterfind session entry persists even after
volume is deleted
-- 
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.