Bug 773379

Summary: rhevm still required realm mapping for deployments
Product: [Retired] CloudForms Cloud Engine Reporter: Dave Johnson <dajohnso>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED NOTABUG QA Contact: wes hayutin <whayutin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, deltacloud-maint, ssachdev
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-11 17:41: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:
Attachments:
Description Flags
ss none

Description Dave Johnson 2012-01-11 17:31:47 UTC 
Description of problem:
==========================
With the recent change of configuring the rhevm provider with the datacenter_id, mapping to a realm should no longer be required since the provider itself points directly at the rhevm realm that instances should be deployed too.  

That isn't the case though, still have to map to a rhevm realm even though configure pointed the provider at it.  It does work this way for vsphere, a realm was not required to launch a imported vsphere image.


Version-Release number of selected component (if applicable):
================================================================
aeolus-all-0.8.0-5.el6.noarch
aeolus-conductor-0.8.0-5.el6.noarch
aeolus-conductor-daemons-0.8.0-5.el6.noarch
aeolus-conductor-doc-0.8.0-5.el6.noarch
aeolus-configure-2.5.0-3.el6.noarch
deltacloud-core-0.5.0-0.rc1.el6.noarch
deltacloud-core-ec2-0.5.0-0.rc1.el6.noarch
deltacloud-core-rhevm-0.5.0-0.rc1.el6.noarch
deltacloud-core-vsphere-0.5.0-0.rc1.el6.noarch
rubygem-aeolus-cli-0.3.0-3.el6.noarch
rubygem-aeolus-image-0.3.0-2.el6.noarch
rubygem-deltacloud-client-0.4.0-3.el6.noarch
Comment 1 Dave Johnson 2012-01-11 17:32:49 UTC 
Created attachment 552177 [details]
ss

I should have mentioned that the following error is displayed in the web ui when this occurs so at the very least, we should correct it.
Comment 2 Dave Johnson 2012-01-11 17:41:52 UTC 
Closing this for a moment