Bug 782854

Summary: mapping a realm to a region for that provider launches the instance for another region
Product: [Retired] CloudForms Cloud Engine Reporter: Shveta <ssachdev>
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-02-14 20:26:09 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
err none

Description Shveta 2012-01-18 17:16:01 UTC
Created attachment 556080 [details]
err

Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Must not be very clear with the bug summary , i created a provider ec2_us_east_1
2. Created a realm us_east
3. Mapped the realm to provider ec2_us_east and realm ec2_us_west_1b

Build/Pushed and launched for ec2_us_east with realm us_east .

Instance was launched in ec2_us_east.

Does that mean that mapping realm to region doesn't matter at all?
  
Actual results:


Expected results:


Additional info:


 rpm -qa|grep aeolus
aeolus-conductor-0.8.0-7.el6.noarch
aeolus-configure-2.5.0-4.el6.noarch
aeolus-conductor-daemons-0.8.0-7.el6.noarch
rubygem-aeolus-image-0.3.0-2.el6.noarch
rubygem-aeolus-cli-0.3.0-3.el6.noarch
aeolus-all-0.8.0-7.el6.noarch
aeolus-conductor-doc-0.8.0-7.el6.noarch

Comment 1 wes hayutin 2012-01-25 17:13:25 UTC
need more details ..

Comment 2 Shveta 2012-02-13 16:01:49 UTC
 Mapped us_east to us_east_1a , but instance was launched in us_east_1b

Comment 3 wes hayutin 2012-02-14 20:26:09 UTC
The provider takes priority over the cluster/back end realm/avail zone

This looks like expected behavior