Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1431523

Summary: [RFE] Gluster get state command should provide remove-brick related information
Product: [Community] GlusterFS Reporter: Darshan <dnarayan>
Component: glusterdAssignee: Atin Mukherjee <amukherj>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: mainlineCC: bugs, sbairagy
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-10 09:48:11 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 Darshan 2017-03-13 05:47:21 UTC 
Description of problem:
Currently "gluster get-state" command does not give any information about remove-brick that happened on a particular volume. It should give full information about the on going / past remove-brick operation on the volume(like things provided by "volume remove-brick status" command), along with other volume details.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
If its very costly to provide this information please enhance gluster get-state to take an option something like "--detail". When "--detail" is provided get-state must provide all the details including the ones which are costly to fetch. Without this option it should only give information which are not costly.

This is needed for tendrl project
Comment 1 Samikshan Bairagya 2017-04-10 09:48:11 UTC 
The remove-brick CLI calls the same RPC that is used by the rebalance status command and both remove-brick and rebalance status essentially show the same information. Therefore closing this bug for the same reasons as mentioned in here: https://bugzilla.redhat.com/show_bug.cgi?id=1431187#c1