Bug 721080

Summary:	rhevm realms need unique names displayed in dc/conductor
Product:	[Retired] CloudForms Cloud Engine	Reporter:	Dave Johnson <dajohnso>
Component:	aeolus-conductor	Assignee:	Angus Thomas <athomas>
Status:	CLOSED ERRATA	QA Contact:	Dave Johnson <dajohnso>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.0.0	CC:	akarol, cpelland, dajohnso, deltacloud-maint, dgao, markmc, mfojtik, morazi, slinaber, ssachdev, whayutin
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	r1173117	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-15 21:44:52 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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