Bug 839945

Summary: Pretty view button in Logs not working
Product: [Retired] CloudForms Cloud Engine Reporter: pushpesh sharma <psharma>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED ERRATA QA Contact: Rehana <aeolus-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.1.0CC: bbandari, dajohnso, dmacpher, morazi
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Clicking the Pretty View button for the Logs page produced no effect. This fix implements the Logs page Pretty View.
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-04 15:13:04 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
Pretty_view_err
none
Pretty_view_working none

Description pushpesh sharma 2012-07-13 09:26:21 UTC
Created attachment 598019 [details]
Pretty_view_err

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.Navigate to Monitor-->Logs-->Pretty View 
2.No Info displayed in any form as displayed in Filter View
3.
  

Additional info:

Comment 2 Dave Johnson 2012-08-07 19:51:55 UTC
THis seems to be fixed now 

aeolus-conductor-0.13.0-0.20120807160018gitc8e87f2.fc16.noarch

Comment 4 pushpesh sharma 2012-09-17 11:29:15 UTC
Verified on:- 

[root@dhcp201-113 ~]# rpm -qa|grep aeolus
aeolus-conductor-0.13.7-1.el6cf.noarch
aeolus-all-0.13.7-1.el6cf.noarch
aeolus-conductor-daemons-0.13.7-1.el6cf.noarch
aeolus-configure-2.8.6-1.el6cf.noarch
aeolus-conductor-doc-0.13.7-1.el6cf.noarch
rubygem-aeolus-cli-0.7.1-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch

Comment 5 pushpesh sharma 2012-09-17 11:29:48 UTC
Created attachment 613634 [details]
Pretty_view_working

Comment 7 errata-xmlrpc 2012-12-04 15:13:04 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-2012-1516.html