Bug 1475331

Summary:	[RFE] get-state CLI should capture rebalance estimation time for the ongoing rebalance for a volume
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Samikshan Bairagya <sbairagy>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED ERRATA	QA Contact:	Bala Konda Reddy M <bmekala>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.3	CC:	rcyriac, rhinduja, rhs-bugs, storage-qa-internal, vbellur
Target Milestone:	---	Keywords:	FutureFeature, ZStream
Target Release:	RHGS 3.3.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8.4-45	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-29 03:29:14 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:
Bug Depends On:
Bug Blocks:	1475686

Description Samikshan Bairagya 2017-07-26 12:52:23 UTC

Description of problem:
get-state CLI should capture rebalance estimation time for the ongoing rebalance for a volume as obtained currently in rebalance status

Comment 2 Samikshan Bairagya 2017-07-26 13:12:18 UTC

Upstream patch: https://review.gluster.org/17862

Comment 5 Bala Konda Reddy M 2017-10-11 15:46:30 UTC

BUILD : 3.8.4-48

Rebalance estimation time is getting captured with gluster get-state

Volume1.rebalance.id: 1bc023ee-0ee7-447f-b2f6-461054900891
Volume1.rebalance.status: started
Volume1.rebalance.failures: 0
Volume1.rebalance.skipped: 2286
Volume1.rebalance.lookedup: 59681
Volume1.rebalance.files: 5091
Volume1.rebalance.data: 712.0MB
Volume1.time_left: 3743

Hence marking it as verified

Comment 8 errata-xmlrpc 2017-11-29 03:29:14 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:3276