Bug 721080 - rhevm realms need unique names displayed in dc/conductor
Summary: rhevm realms need unique names displayed in dc/conductor
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-13 16:33 UTC by Dave Johnson
Modified: 2012-05-15 21:44 UTC (History)
11 users (show)

Fixed In Version: r1173117
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-15 21:44:52 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0583 0 normal SHIPPED_LIVE new packages: aeolus-conductor 2012-05-15 22:31:59 UTC

Description Dave Johnson 2011-07-13 16:33:40 UTC 
When you have a single datacenter with multiple clusters underneath it, the datacenter name is listed multiple times within deltacloud core (& conductor) for each cluster. We need to maybe append the datacenter name with each '-clusterName' so the user can determine the appropriate cluster. 

I opened a bug with them as follows and Wes asked for a tracker here.

https://issues.apache.org/jira/browse/DTACLOUD-57
Comment 1 wes hayutin 2011-07-21 13:24:06 UTC 
taking off blocker
Comment 2 Francesco Vollero 2011-09-20 12:44:46 UTC 
Bug solved in revision r1173117
Comment 3 wes hayutin 2011-09-28 16:37:55 UTC 
making sure all the bugs are at the right version for future queries
Comment 5 Steve Linabery 2012-01-10 22:03:18 UTC 
Blindly setting this to ON_QA in the belief that a fix is included in the latest aeolus packages.
Comment 6 Dave Johnson 2012-01-11 16:03:27 UTC 
moving to verified, this has been resolved for some time
Comment 8 errata-xmlrpc 2012-05-15 21:44:52 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
Note You need to log in before you can comment on or make changes to this bug.