Bug 800726 - Cloud: link to be replaced with cloud
Summary: Cloud: link to be replaced with cloud
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: beta5
Assignee: Angus Thomas
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-07 05:04 UTC by Aziza Karol
Modified: 2012-12-13 19:49 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-13 19:49:34 UTC


Attachments (Terms of Use)
cloud (193.66 KB, image/png)
2012-03-07 05:06 UTC, Aziza Karol
no flags Details

Description Aziza Karol 2012-03-07 05:04:49 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.Navigate to new component outline.

colon from the link cloud: should be removed. see attached screenshot





Additional info:
rpm -qa | grep aeolus
aeolus-conductor-doc-0.8.0-41.el6.noarch
aeolus-conductor-daemons-0.8.0-41.el6.noarch
rubygem-aeolus-cli-0.3.0-13.el6.noarch
aeolus-all-0.8.0-41.el6.noarch
aeolus-conductor-0.8.0-41.el6.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-configure-2.5.0-18.el6.noarch

Comment 1 Aziza Karol 2012-03-07 05:06:48 UTC
Created attachment 568132 [details]
cloud

Comment 2 Angus Thomas 2012-09-06 10:26:45 UTC
The nav label is now working correctly. Showing "Cloud: <name>", where <name> is the name of the specific cloud.

Comment 3 Aziza Karol 2012-09-18 06:46:31 UTC
Showing "Cloud: <name>", where <name> is the name of the specific cloud.

verified:
rpm -qa | grep aeolus
aeolus-conductor-0.13.7-1.el6cf.noarch
aeolus-all-0.13.7-1.el6cf.noarch
rubygem-aeolus-cli-0.7.1-1.el6cf.noarch
aeolus-conductor-doc-0.13.7-1.el6cf.noarch
aeolus-configure-2.8.6-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-conductor-daemons-0.13.7-1.el6cf.noarch


Note You need to log in before you can comment on or make changes to this bug.