Bug 786262

Summary: provider -> "Cloud Resource Cluster" misrenders page
Product: [Retired] CloudForms Cloud Engine Reporter: wes hayutin <whayutin>
Component: aeolus-conductorAssignee: Tomas Sedovic <tsedovic>
Status: CLOSED ERRATA QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, deltacloud-maint, ssachdev, tsedovic
Target Milestone: beta   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://qeblade30.rhq.lab.eng.bos.redhat.com/conductor/providers/9/edit
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-15 22:25:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
ss
none
nav bar none

Description wes hayutin 2012-01-31 21:03:17 UTC
Created attachment 558705 [details]
ss

Description of problem:

nav to..
1. provider -> ec2,vsphere etc
2. click "cloud resource cluster"
3. click the name of the cloud resouce cluster, 

we loose the top nav bar..

Comment 1 Tomas Sedovic 2012-02-02 14:48:19 UTC
Patch sent to the list:

https://fedorahosted.org/pipermail/aeolus-devel/2012-February/008580.html

Comment 2 Tomas Sedovic 2012-02-03 15:05:50 UTC
Fixed in commit: 3a5aa30787591de2f6e9571cd39d977a2e725713

Comment 3 Aziza Karol 2012-02-08 05:00:27 UTC
Nav  bar displayed  when clicked on cloud resource cluster name.
see attached screenshot.

verified:
rpm -qa | grep aeolus
aeolus-conductor-0.8.0-23.el6.noarch
rubygem-aeolus-cli-0.3.0-8.el6.noarch
aeolus-configure-2.5.0-12.el6.noarch
rubygem-aeolus-image-0.3.0-7.el6.noarch
aeolus-all-0.8.0-23.el6.noarch
aeolus-conductor-doc-0.8.0-23.el6.noarch
aeolus-conductor-daemons-0.8.0-23.el6.noarch

Comment 4 Aziza Karol 2012-02-08 05:01:15 UTC
Created attachment 560124 [details]
nav bar

Comment 5 errata-xmlrpc 2012-05-15 22:25:57 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-0583.html