Bug 1037583 - [RHSC] After retaining a brick using the Retain button in the status dialog, the 'Stopped At' field does not appear
Summary: [RHSC] After retaining a brick using the Retain button in the status dialog, ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.1
Hardware: Unspecified
OS: Unspecified
medium
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-12-03 12:10 UTC by Shruti Sampat
Modified: 2015-05-13 16:30 UTC (History)
7 users (show)

Fixed In Version: cb11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-25 08:07:26 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 21966 0 None None None Never

Description Shruti Sampat 2013-12-03 12:10:52 UTC
Description of problem:
-----------------------

After retaining a brick that was selected for removal, using the Retain button in the status dialog, the 'Stopped At' field does not get displayed. Closing the dialog and opening it again displays the Stopped At field.

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

How reproducible:
Always

Steps to Reproduce:
1. Start remove-brick operation on a volume.
2. After data migration is completed, retain the brick using the retain button in the status dialog.


Actual results:
The stopped at field is not displayed on the status dialog.

Expected results:
The stopped at field should be displayed once the brick is retained.

Additional info:

Comment 2 Shruti Sampat 2013-12-18 15:46:07 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 08:07: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.

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.