Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 669246

Summary: Launching an instance fails in Jan 4th build
Product: [Retired] CloudForms Cloud Engine Reporter: wes hayutin <whayutin>
Component: aeolus-conductorAssignee: Scott Seago <sseago>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: low    
Version: 0.3.1CC: deltacloud-maint, morazi, ssachdev
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://10.16.120.28/deltacloud/builds/new?template_id=2
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-09 17:34:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
instance launch error
none
instance details w/ error none

Description wes hayutin 2011-01-13 01:19:59 UTC
Created attachment 473171 [details]
instance launch error

Launcing an instance in the Jan 4th build fails.  The only repository that is available is x86_64 Fedora 13.  To reproduce, create a template, when you're on the page where you choose the provider format, notice the Hardware Profile its being build for.. "small"
Please look a the screenshot for details here:

small in ec2 is x86, however we are building an x86_64 image.  

Continue to build the image, it will build. 
Next try to launch the instance.  You will get the following message 

"The requested instance type's architecture (x86_64) does not match the architecture in the manifest for ami-6226d30b (i386):"



0.16.120.28 - - [13/Jan/2011 09:01:28] "GET /api HTTP/1.1" 200 932 0.0254
127.0.0.1 - - [13/Jan/2011 09:01:29] "GET /api/instances HTTP/1.1" 200 65 0.5480
Deltacloud::BackendError - The requested instance type's architecture (x86_64) does not match the architecture in the manifest for ami-6226d30b (i386):
 ././lib/deltacloud/base_driver/base_driver.rb:251:in `safely'
 ././lib/deltacloud/base_driver/base_driver.rb:250:in `each'
 ././lib/deltacloud/base_driver/base_driver.rb:250:in `safely'
 ././lib/deltacloud/drivers/ec2/ec2_driver.rb:184:in `create_instance'
 ././server.rb:202
 ././lib/sinatra/rabbit.rb:62:in `instance_eval'
 ././lib/sinatra/rabbit.rb:62:in `POST /api/instances'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:863:in `call'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:863:in `route'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:521:in `instance_eval'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:521:in `route_eval'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:500:in `route!'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:497:in `catch'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:497:in `route!'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:476:in `each'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:476:in `route!'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:601:in `dispatch!'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:411:in `call!'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in `instance_eval'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in `invoke'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in `catch'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in `invoke'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:411:in `call!'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:399:in `call'
 /usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/context.rb:22:in `call'
 /usr/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/methodoverride.rb:24:in `call'
 /usr/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/commonlogger.rb:18:in `call'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:979:in `call'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:1005:in `synchronize'
 /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:979:in `call'
 /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/stats.rb:24:in `call'
 /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/stats.rb:33:in `log'
 /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/stats.rb:24:in `call'
 /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/connection.rb:76:in `pre_process'
 /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/connection.rb:74:in `catch'
 /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/connection.rb:74:in `pre_process'
 /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1060:in `call'
 /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1060:in `spawn_threadpool'
 /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `initialize'
 /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `new'
 /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `spawn_threadpool'
 /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1049:in `defer'
 /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/connection.rb:54:in `process'
 /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/connection.rb:42:in `receive_data'
 /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run_machine'
 /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run'
 /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/backends/base.rb:57:in `start'
 /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/server.rb:156:in `start'
 /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/controllers/controller.rb:80:in `start'
 /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/runner.rb:177:in `send'
:

Comment 1 wes hayutin 2011-02-22 21:01:24 UTC
looks like this is still an issue.. reopening

Comment 2 Dave Johnson 2011-02-24 22:32:57 UTC
Created attachment 480872 [details]
instance details w/ error

not sure if this will help but this is what the instance details shows

Comment 3 Mike Orazi 2011-02-25 19:04:12 UTC
This bug has morphed a little bit, but the new version of a boxgrinder rpm (rubygem-boxgrinder-build-s3-delivery-plugin.noarch     0.0.5.1-1.fc14) addresses the underlying issue of being unable to launch the instance.

The rpm in question is currently being promoted to stable in fedora and should become widely available shortly.

Comment 4 wes hayutin 2011-03-11 16:41:54 UTC
verified.. launching instances is working in


[root@nec-em15 ~]# rpm -qa | grep aeolus
aeolus-conductor-0.0.3-0.fc1420110309220719git7f7738b.x86_64
aeolus-configure-2.0.0-4.fc1420110309224940gite08f2c6.noarch
aeolus-conductor-doc-0.0.3-0.fc1420110309220719git7f7738b.x86_64
aeolus-conductor-debuginfo-0.0.3-0.fc1420110309220719git7f7738b.x86_64
aeolus-conductor-daemons-0.0.3-0.fc1420110309220719git7f7738b.x86_64
[root@nec-em15 ~]#

Comment 5 wes hayutin 2011-03-16 13:55:40 UTC
*** Bug 688048 has been marked as a duplicate of this bug. ***

Comment 6 wes hayutin 2011-03-16 13:56:44 UTC
this issue was "rediscovered" in https://bugzilla.redhat.com/show_bug.cgi?id=688048
Placing on_qa to retest against latest builds

Comment 7 wes hayutin 2011-04-18 17:58:10 UTC
 fourth	running	testBlank	ec2-174-129-75-158.compute-1.amazonaws.com	ec2-us-east-1	wes hay


[root@ip-10-80-242-101 aeolus-conductor]# rpm -qa | grep aeolus
aeolus-conductor-doc-0.0.3-6.el6.x86_64
aeolus-conductor-0.0.3-6.el6.x86_64
aeolus-conductor-daemons-0.0.3-6.el6.x86_64
aeolus-configure-2.0.0-8.el6.noarch
[root@ip-10-80-242-101 aeolus-conductor]# rpm -qa | grep factory
rubygem-image_factory_console-0.2.0-2.el6_0.20110401225248git6800ed8.noarch
rubygem-image_factory_connector-0.0.2-2.el6.20110414153545git257f8a3.noarch
imagefactory-0.1.6.2_8_gbcb427d-2.el6.noarch

Comment 8 wes hayutin 2011-08-01 19:58:36 UTC
release pending...

Comment 9 wes hayutin 2011-08-01 19:59:31 UTC
release pending...

Comment 11 wes hayutin 2011-12-08 13:55:48 UTC
perm close

Comment 12 wes hayutin 2011-12-08 13:58:58 UTC
closing out old bugs