Bug 867379

Summary: volume info displays information about a brick that has already been removed
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Vidya Sakar <vinaraya>
Component: glusterdAssignee: Amar Tumballi <amarts>
Status: CLOSED NOTABUG QA Contact: Sudhir D <sdharane>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 2.0CC: gluster-bugs, kdhananj, kparthas, rfortier, rhs-bugs, vbellur, vraman
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 866916 Environment:
Last Closed: 2012-10-18 06:07:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 866916    
Bug Blocks:    

Description Vidya Sakar 2012-10-17 11:55:59 UTC 
+++ This bug was initially created as a clone of Bug #866916 +++

Description of problem:
Volume info command continues to display information about a brick even after its removal.

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


How reproducible:


Steps to Reproduce:
1.In a two-machine cluster, create a volume with two bricks, one on each machine (say B1 on M1 and B2 on M2).
2.Execute remove-brick on M1 to remove the brick on M2 (i.e., B2).
3.Do volume info on M1.
  
Actual results:

Volume info displays information about B2, even after its removal.

Expected results:

Volume info should only display information about B1.

Additional info:

[root@kd glusterfs]# gluster volume info xyz
 
Volume Name: xyz
Type: Distribute
Volume ID: d336401f-ecb2-428b-8a4c-dabfd8b1851f
Status: Started
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: 192.168.122.1:/export2/xyza
Brick2: 192.168.122.250:/home/xyzab
----------------------------------------------------------
[root@kd glusterfs]# gluster volume remove-brick xyz 192.168.122.250:/home/xyzab start
volume remove-brick: success
---------------------------------------------------------
[root@kd glusterfs]# gluster volume info xyz
 
Volume Name: xyz
Type: Distribute
Volume ID: d336401f-ecb2-428b-8a4c-dabfd8b1851f
Status: Started
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: 192.168.122.1:/export2/xyza
Brick2: 192.168.122.250:/home/xyzab
----------------------------------------------------------
[root@kd glusterfs]# gluster volume remove-brick xyz 192.168.122.250:/home/xyzab commit
volume remove-brick: success
---------------------------------------------------------
[root@kd glusterfs]# gluster volume info xyz
 
Volume Name: xyz
Type: Distribute
Volume ID: d336401f-ecb2-428b-8a4c-dabfd8b1851f
Status: Started
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: 192.168.122.1:/export2/xyza
Brick2: 192.168.122.250:/home/xyzab
Comment 1 krishnan parthasarathi 2012-10-18 06:07:56 UTC 
This bug is not applicable to RHS-2.0. It is only seen on master since http://review.gluster.org/4057 commit.