Bug 962878 - A downed node does not show up at all in volume status output
Summary: A downed node does not show up at all in volume status output
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: pre-release
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-14 16:40 UTC by hans
Modified: 2015-10-22 15:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-22 15:40:20 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description hans 2013-05-14 16:40:34 UTC 
Description of problem:

In a distribute-replicate setup with multiple nodes and a node down the 'volume status' command gives no hint of an entire node being down.

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

3.3git-v3.3.2qa2-3-g3490689

How reproducible:

Always

Steps to Reproduce:
1. Stop a node in distribute-replicate setup
2. Run 'gluster volume status'
3. See that the node which is down is not mentioned as being down.
  
Actual results:

Only the nodes that are up are shown in the status output.

Expected results:

A not-OK message per unavailable brick.
Comment 1 Kaleb KEITHLEY 2015-10-22 15:40:20 UTC 
pre-release version is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.
Note You need to log in before you can comment on or make changes to this bug.