Bug 1518648

Summary:	On grafana dashboard, rebalanced files size is not having any units (MB or GB)
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Bala Konda Reddy M <bmekala>
Component:	web-admin-tendrl-monitoring-integration	Assignee:	Ankush Behl <anbehl>
Status:	CLOSED ERRATA	QA Contact:	Rochelle <rallan>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.3	CC:	nthomas, rallan, rghatvis, rhs-bugs, sanandpa, sankarshan
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tendrl-monitoring-integration-1.5.4-11.el7rhgs.noarch	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-18 04:38:26 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 Bala Konda Reddy M 2017-11-29 12:02:57 UTC

Description of problem:
Rebalance information on grafana is proper. In tendrl-gluster-volumes page, Rebalance widget for size it is mentioned as normal number.


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


How reproducible:
1/1

Steps to Reproduce:
1. Create a replica volume (2*3). 
2. While IO's are going on, Perform add brick.
3. Start rebalance

Actual results:
Rebalance is showing in-progress but the size of rebalanced files is not having any units


Expected results:
Rebalanced files should show the size in units in MB or GB

Additional info:

Comment 5 Bala Konda Reddy M 2017-12-05 08:59:05 UTC

Verified with tendrl-monitoring-integration-1.5.4-11.el7rhgs.noarch

On successfully imported cluster, performed add-brick to a replica 3 volume and the data on the dashboard is consistent and the size of rebalanced files is in MiB as expected.

Hence marking it as verified.

Comment 7 errata-xmlrpc 2017-12-18 04:38:26 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/RHEA-2017:3478