Bug 1377199

Summary: RFE: remove-brick status [failed|skipped]
Product: [Community] GlusterFS Reporter: Milan Zink <mzink>
Component: distributeAssignee: bugs <bugs>
Status: CLOSED EOL QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.7.9CC: amukherj, bugs, nbalacha
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-08 10:58:26 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:

Description Milan Zink 2016-09-19 07:37:38 UTC
Description of problem:

[RFE] Please add a new sub-command to 'gluster volume remove-brick <vol> <peer>:<brick> status [failed|skipped]'.

This command will list failed or skipped entries if any. I think this will be useful. Now, the only way to find problematic files is search in logs.

Comment 1 Atin Mukherjee 2016-09-19 08:13:00 UTC
Nithya - can you weigh in this request with your thoughts?

Comment 2 Nithya Balachandran 2016-10-24 09:34:44 UTC
Would writing these entries to a separate file be acceptable? The command if added later could simply parse these files and display the entries.

Comment 3 Kaushal 2017-03-08 10:58:26 UTC
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.