Bug 1431523 - [RFE] Gluster get state command should provide remove-brick related information
Summary: [RFE] Gluster get state command should provide remove-brick related information
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Atin Mukherjee
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-13 05:47 UTC by Darshan
Modified: 2017-04-10 09:48 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-04-10 09:48:11 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.