Bug 1286572

Summary:	[FEAT] DHT - rebalance - rebalance status o/p should be different for 'fix-layout' option, it should not show 'Rebalanced-files' , 'Size', 'Scanned' etc as it is not migrating any files.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Susant Kumar Palai <spalai>
Component:	distribute	Assignee:	Nithya Balachandran <nbalacha>
Status:	CLOSED ERRATA	QA Contact:	Prasad Desala <tdesala>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rhgs-3.1	CC:	kramdoss, lbailey, mzywusko, nbalacha, racpatel, rcyriac, rgowdapp, rhinduja, rhs-bugs, sankarshan, spalai, vbellur
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	RHGS 3.2.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	triaged, dht-rebalance-usability, dht-gss, dht-3.2.0-proposed
Fixed In Version:	glusterfs-3.8.4-1	Doc Type:	Enhancement
Doc Text:	Previously, the output of the 'gluster volume rebalance VOLNAME status' command attempted to display status details for fix-layout operations despite this operation not populating the output with details of rebalanced files, scanned files, failures, and size. The unpopulated sections have now been removed so that only status and elapsed time on each node are shown.	Story Points:	---
Clone Of:	890640	Environment:
Last Closed:	2017-03-23 05:25:17 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:	890640
Bug Blocks:	1351503, 1351530

Comment 8 Prasad Desala 2016-11-25 07:03:06 UTC

Verified this BZ on glusterfs version: 3.8.4-5.el7rhgs.x86_64.

When rebalance is started with fix-layout option, the rebalance status output is now showing the status of layout fixing.

Moving this BZ to Verified, will raise a new BZ if any on this separately.

Comment 12 errata-xmlrpc 2017-03-23 05:25:17 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://rhn.redhat.com/errata/RHSA-2017-0486.html