Hide Forgot
Created attachment 561817 [details] ec2_1a_mapped cluster screenshot Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Created an instance in cluster which is mapped to "ec2-us-east-1: us-east-1a" provider resource cluster( P FA:ec2_1a_mapped cluster.png,instance creation on 1A.png) 2. But the instance got launched on the us-east-1c(P FA:instance on 1c.png) Delta cloud log: I, [2012-02-14T03:26:42.344545 #8510] INFO -- : New Aws::Ec2 using per_thread-connection mode W, [2012-02-14T03:26:42.356132 #8510] WARN -- : Rightscale::HttpConnection : request failure count: 1, exception: #<Errno::EPIPE: Broken pipe> I, [2012-02-14T03:26:42.356248 #8510] INFO -- : Opening new HTTPS connection to ec2.us-east-1.amazonaws.com:443 I, [2012-02-14T03:26:53.960162 #8510] INFO -- : New Aws::Ec2 using per_thread-connection mode W, [2012-02-14T03:26:53.964855 #8510] WARN -- : Rightscale::HttpConnection : request failure count: 1, exception: #<Errno::EPIPE: Broken pipe> I, [2012-02-14T03:26:53.964989 #8510] INFO -- : Opening new HTTPS connection to ec2.us-east-1.amazonaws.com:443 I, [2012-02-14T03:26:57.429038 #8510] INFO -- : New Aws::Ec2 using per_thread-connection mode I, [2012-02-14T03:26:57.437926 #8510] INFO -- : Launching instance of image ami-b9a172d0 for AKIAJZG5XB3O6GU7O6SQ, key: EC2_1a_Instance_Fedora-15-32bit_1329208013_key_70191509501660, groups: W, [2012-02-14T03:26:57.439578 #8510] WARN -- : Rightscale::HttpConnection : request failure count: 1, exception: #<Errno::EPIPE: Broken pipe> I, [2012-02-14T03:26:57.439689 #8510] INFO -- : Opening new HTTPS connection to ec2.us-east-1.amazonaws.com:443 I, [2012-02-14T03:27:43.367088 #8510] INFO -- : New Aws::Ec2 using per_thread-connection mode W, [2012-02-14T03:27:43.371655 #8510] WARN -- : Rightscale::HttpConnection : request failure count: 1, exception: #<Errno::EPIPE: Broken pipe> I, [2012-02-14T03:27:43.371765 #8510] INFO -- : Opening new HTTPS connection to ec2.us-east-1.amazonaws.com:443 I, [2012-02-14T03:28:44.405461 #8510] INFO -- : New Aws::Ec2 using per_thread-connection mode W, [2012-02-14T03:28:44.415460 #8510] WARN -- : Rightscale::HttpConnection : request failure count: 1, exception: #<Errno::EPIPE: Broken pipe> I, [2012-02-14T03:28:44.415572 #8510] INFO -- : Opening new HTTPS connection to ec2.us-east-1.amazonaws.com:443 I, [2012-02-14T03:29:45.432569 #8510] INFO -- : New Aws::Ec2 using per_thread-connection mode Actual results: instance getting launched on us-east-1c instead on us-east-1a Expected results: Instance is expected to be launched on the selected region(which is mapped during cluster creation) Additional info: rpm -qa | grep aeolus aeolus-conductor-0.8.0-26.el6.noarch aeolus-conductor-doc-0.8.0-26.el6.noarch aeolus-configure-2.5.0-13.el6.noarch aeolus-all-0.8.0-26.el6.noarch rubygem-aeolus-image-0.3.0-7.el6.noarch rubygem-aeolus-cli-0.3.0-8.el6.noarch aeolus-conductor-daemons-0.8.0-26.el6.noarch
Created attachment 561818 [details] instance creation on 1A added screenshot
Created attachment 561819 [details] instance on 1c added screenshot file
hin server (localhost:3002) [deltacloud-mock][3332]: Processing /api/instances (for 127.0.0.1 at Tue Feb 14 11:11:19 -0500 2012) [POST] [EC2] thin server (localhost:3002) [deltacloud-mock][3332]: Parameters: {"name"=>"us-east-i386-wes2-us-east-i386-wes", "hwp_memory"=>"1740.8", "hwp_storage"=>"160", "hwp_id"=>"m1.small", "image_id"=>"ami-cdd306a4", "keyname"=>"us-east-i386-wes2_us-east-i386-wes_1329235876_key_70191505496800", "hwp_cpu"=>"1"} thin server (localhost:3002) [deltacloud-mock][3332]: Provider: us-east-1 thin server (localhost:3002) [deltacloud-mock][3332]: Authentication: Basic thin server (localhost:3002) [deltacloud-mock][3332]: Server: thin 1.2.11 codename Bat-Shit Crazy thin server (localhost:3002) [deltacloud-mock][3332]: Accept: application/xml I, [2012-02-14T11:11:19.254148 #3332] INFO -- : New Aws::Ec2 using per_thread-connection mode I, [2012-02-14T11:11:19.255466 #3332] INFO -- : Launching instance of image ami-cdd306a4 for AKIAJZG5XB3O6GU7O6SQ, key: us-east-i386-wes2_us-east-i386-wes_1329235876_key_701915054 so.. when we setup a realm for ec2 we specify the ec2 availability zone. When we launch an instance I'm noticing that we do not send the availability zone as a parameter. Do we not guarantee where its launched (guessing) but are we not even sending the zone to ec2?
ah.. removing the provider mapping in the realm fixes this.. notice the avail zone is now mapped.. (localhost:3002) [deltacloud-mock][3332]: Processing /api/instances (for 127.0.0.1 at Tue Feb 14 11:22:24 -0500 2012) [POST] [EC2] thin server (localhost:3002) [deltacloud-mock][3332]: Parameters: {"realm_id"=>"us-east-1b", "name"=>"us-east-i386-wes-3-us-east-i386-wes", "hwp_memory"=>"1740.8", "hwp_storage"=>"160", "hwp_id"=>"m1.small", "image_id"=>"ami-cdd306a4", "keyname"=>"us-east-i386-wes-3_us-east-i386-wes_1329236542_key_70191504759480", "hwp_cpu"=>"1"} thin server (localhost:3002) [deltacloud-mock][3332]: Provider: u