Bug 1027136 - [RHSC] Host column in the remove-brick status dialog should be sorted.
Summary: [RHSC] Host column in the remove-brick status dialog should be sorted.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.1
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: RHGS 2.1.2
Assignee: anmol babu
QA Contact: Shruti Sampat
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-06 08:56 UTC by Shruti Sampat
Modified: 2015-05-13 16:27 UTC (History)
7 users (show)

Fixed In Version: cb9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-25 07:59:25 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:0208 0 normal SHIPPED_LIVE Red Hat Storage 2.1 enhancement and bug fix update #2 2014-02-25 12:20:30 UTC
oVirt gerrit 20746 0 None None None Never

Description Shruti Sampat 2013-11-06 08:56:49 UTC
Description of problem:
------------------------
The hosts column in the remove-brick status dialog is not sorted, which causes the rows to flip, each time refresh occurs. The hosts column needs to be sorted based on the names of the hosts.

Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.1.2-0.22.master.el6_4 

How reproducible:
Always

Steps to Reproduce:
1. Start remove-brick on a volume.
2. Click on the arrow beside the remove-brick icon in the Activities column, and click on Status button.

Actual results:
Hosts column is not sorted, and the rows keep flipping each time the refresh occurs.

Expected results:
Host column needs to be sorted based on host-names.

Additional info:

Comment 2 Shruti Sampat 2013-11-26 12:40:11 UTC
Verified as fixed in Red Hat Storage Console Version: 2.1.2-0.25.master.el6_5. Hosts now listed in sorted order.

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


Note You need to log in before you can comment on or make changes to this bug.