Bug 807428

Summary: Gluster volume status command produces truncated result when a node is down
Product: [Community] GlusterFS Reporter: Gareth Bult <gareth>
Component: glusterdAssignee: Kaushal <kaushal>
Status: CLOSED CURRENTRELEASE QA Contact: Anush Shetty <ashetty>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.3-betaCC: gluster-bugs, rfortier, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: glusterfs-3.4.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-24 13:46:50 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 817967    

Description Gareth Bult 2012-03-27 14:40:11 EDT
gluster volume stats

- works OK if all nodes are up, but breaks it one or more nodes are not available. Typically the list of bricks stops as soon as it comes to a brick on a downed node.

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

To reproduce:

visit random node
"service glusterd stop"
visit random client
"gluster volume status"
- result should be truncated when it reached downed node.

Have tried on 2 stripe replica and 4 stripe replica.  


The faulty node must contain an active volume.
The output of "gluster volume status" will be different depending on which node you take out.
Comment 1 Kaushal 2012-03-30 01:00:29 EDT
Fixed in change http://review.gluster.com/3016 for bug https://bugzilla.redhat.com/show_bug.cgi?id=803676
Comment 2 Anush Shetty 2012-05-31 05:27:09 EDT
Verified with 3.3.0qa45