Bug 962878 - A downed node does not show up at all in volume status output
A downed node does not show up at all in volume status output
Status: CLOSED EOL
Product: GlusterFS
Classification: Community
Component: core (Show other bugs)
pre-release
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: bugs@gluster.org
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-14 12:40 EDT by hans
Modified: 2015-10-22 11:40 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-10-22 11:40:20 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description hans 2013-05-14 12:40:34 EDT
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 11:40:20 EDT
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.