Bug 1019560 - [RHS-C] Remove bricks status dialog shows "Started At" field as a text box. It should be a label.
Summary: [RHS-C] Remove bricks status dialog shows "Started At" field as a text box. I...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhsc
Version: 2.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: RHGS 2.1.2
Assignee: Shubhendu Tripathi
QA Contact: Prasanth
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-16 05:39 UTC by Shubhendu Tripathi
Modified: 2015-05-13 16:31 UTC (History)
4 users (show)

Fixed In Version: cb4
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-25 07:51:46 UTC
Target Upstream Version:


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 20181 0 None None None Never

Description Shubhendu Tripathi 2013-10-16 05:39:30 UTC
Description of problem:
The remove bricks status dialog shows the field "Started At" as a text box.
It should be displayed as label with correct value populated in it.

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


How reproducible:
Alway

Steps to Reproduce:
1. Go to Volumes tab and select a volume
2. Select the bricks sub-tab and select a brick from the list
3. Start remove brick by clicking the menu option "Remove"
4. Click the drop down menu option from the Activities column. It pops up the "Remove Bricks Status" dialog.
5. Check the "Started At" field value on the dialog

Actual results:
The field value is shown as a text box

Expected results:
The field value should be shown as a label with properly populated value

Additional info:

Comment 2 Dustin Tsang 2013-10-28 13:52:10 UTC
verified as fixed in rhsc-cb5

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