Bug 850446

Summary: Providing detailed status about Volume
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Vidya Sakar <vinaraya>
Component: rhscAssignee: Shubhendu Tripathi <shtripat>
Status: CLOSED ERRATA QA Contact: Prasanth <pprakash>
Severity: urgent Docs Contact:
Priority: medium    
Version: unspecifiedCC: gluster-bugs, mmahoney, pprakash, rfortier, sabose, sdharane, shaines, shtripat, ssampat
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-23 22:26:05 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:
Bug Depends On: 877961, 918453    
Bug Blocks: 865324    
Attachments:
Description Flags
Empty Brick Details Dialogue none

Description Vidya Sakar 2012-08-21 15:25:58 UTC
UI should leverage and display the detailed output provided by commands such as 'volume status'.

Comment 2 Shireesh 2012-10-31 14:06:46 UTC
Upstream patches:

http://gerrit.ovirt.org/7807
http://gerrit.ovirt.org/8898

Comment 3 Shireesh 2012-11-16 09:52:07 UTC
Patches have been pulled to downstream as part of the periodic rebase with upstream, and are available in the latest QE drop.

Comment 4 Prasanth 2012-11-27 06:42:33 UTC
Moving the bug back to ASSIGNED as this feature is not working (Bug 877961) in the latest QE drop: rhsc-2.1-qa18.el6ev.noarch

Comment 5 Matt Mahoney 2013-02-27 20:29:41 UTC
Created attachment 703625 [details]
Empty Brick Details Dialogue

Comment 6 Matt Mahoney 2013-02-27 20:32:32 UTC
First attempt at displaying brick details populates as expected. Close the brick details dialogue box, and then reopen for the same or any other brick results in the details being empty (see attachment).

Comment 8 Matt Mahoney 2013-04-29 17:24:48 UTC
Verified in QA10

Comment 10 Scott Haines 2013-09-23 22:26:05 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/RHBA-2013-1262.html