Bug 688177

Summary:	create instance form needs realm field disabled
Product:	[Retired] CloudForms Cloud Engine	Reporter:	Dave Johnson <dajohnso>
Component:	aeolus-conductor	Assignee:	Mike Orazi <morazi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Dave Johnson <dajohnso>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.3.1	CC:	akarol, cpelland, dajohnso, deltacloud-maint, dgao, ssachdev, whayutin
Target Milestone:	beta
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-14 16:10:45 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-03-16 14:35:24 UTC

Description of problem:
If you create a realm and then start a instance adding it to the realm you created, the instance will not transition from new (I am thinking condor just ignores it) and the end user get zero feedback as to why it is not starting

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


How reproducible:


Steps to Reproduce:
1.  create a realm
2.  create a instance from a pre-existing built template adding it to the new realm
  
Actual results:
instance stays in 'new' state

Expected results:
realm is ignored (since it really isn't supported) and the instance starts

Additional info:

Comment 1 wes hayutin 2011-12-08 14:12:31 UTC

perm close