Bug 1020883

Summary: [RHSC] In the task tab, show the size of rebalanced files in MB or GB
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Shruti Sampat <ssampat>
Component: rhscAssignee: anmol babu <anbabu>
Status: CLOSED ERRATA QA Contact: Shruti Sampat <ssampat>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 2.1CC: dpati, dtsang, knarra, mmahoney, pprakash, rhs-bugs, sdharane
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 2.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cb11 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-25 07:40:52 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:
Attachments:
Description Flags
screenshot none

Description Shruti Sampat 2013-10-18 12:37:57 UTC
Created attachment 813766 [details]
screenshot

Description of problem:
-------------------------
In the task tab, when the task for rebalance is displayed, the size of files moved is shown in bytes.  For e.g. - 

Rebalancing Gluster Volume dis_vol in Cluster test.( FINISHED Files [scanned: 281, moved: 12, failed: 0], Total size moved: 12582912000)

It would be better to show the size in MB or GB.

Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.1.2-0.0.scratch.beta1.el6_4 

How reproducible:
Always

Steps to Reproduce:
1. Start rebalance on a volume from the Console.
2. Monitor the task created for the rebalance in the tasks tab.

Actual results:
The size of files rebalanced is shown in bytes.

Expected results:
Show the size in larger units like mega bytes or giga bytes.

Additional info:

Comment 2 Shruti Sampat 2013-12-20 11:37:18 UTC
Verified as fixed in Red Hat Storage Console Version: 2.1.2-0.27.beta.el6_5.

Comment 4 errata-xmlrpc 2014-02-25 07:40:52 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.

http://rhn.redhat.com/errata/RHEA-2014-0208.html