Bug 1663243

Summary:	rebalance status does not display localhost statistics when op-version is not bumped up
Product:	[Community] GlusterFS	Reporter:	Sanju <srakonde>
Component:	glusterd	Assignee:	Sanju <srakonde>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-25 16:32:53 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 Sanju 2019-01-03 14:36:20 UTC

Description of problem:
rebalance status command is not showing information of local host when the cluster is not running with the current max op version.

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


How reproducible:
always

Steps to Reproduce:
1. set the cluster op-version less than the max op version
2. create and start a volume
3. start rebalance for volume and check for rebalance status

Actual results:
In the output of "rebalance status" information related to localhost is not displayed.

Expected results:
It should display te information of localhost as well.

Additional info:

Comment 1 Sanju 2019-01-04 06:02:42 UTC

*** Bug 1663244 has been marked as a duplicate of this bug. ***

Comment 2 Worker Ant 2019-01-04 11:49:11 UTC

REVIEW: https://review.gluster.org/21992 (glusterd: rebalance status should display information of localhost) posted (#1) for review on master by Sanju Rakonde

Comment 3 Worker Ant 2019-01-07 02:45:20 UTC

REVIEW: https://review.gluster.org/21992 (glusterd: rebalance status should display information of localhost) posted (#3) for review on master by Sanju Rakonde

Comment 4 Shyamsundar 2019-03-25 16:32:53 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report.

glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/