Bug 723680

Summary:

deployable should check image platform matches hwp given

Product:

[Retired] CloudForms Cloud Engine

Reporter:

Dave Johnson <dajohnso>

Component:

aeolus-conductor

Assignee:

Jan Provaznik <jprovazn>

Status:

CLOSED ERRATA

QA Contact:

Dave Johnson <dajohnso>

Severity:

unspecified

Docs Contact:

Priority:

unspecified

Version:

1.0.0

CC:

akarol, cpelland, dajohnso, deltacloud-maint, dgao, redakkan, slinaber, 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:

2012-05-15 21:48:13 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
useless error	none
error Screenshot	none

Description Dave Johnson 2011-07-20 19:33:28 UTC

Description of problem:
========================
I created a F15 i386 image and pushed it into EC2.  I then created a deployable xml for the image but accidentally used the default hwp1 which is for x86_64 architectures.  The UI allowed me to launch the deployable which failed with a create_instance_failure which didn't really help, digging through the rails log I noticed the issue.  The frontend should check this to prevent the user from encountering the same issue. 

Version-Release number of selected component (if applicable):
=============================================================
[root@ibm-x3650-04 ~]# rpm -qa | grep aeolus
rubygem-aeolus-image-0.0.1-1.el6.20110719153543gitd39221e.noarch
aeolus-conductor-0.3.0-0.el6.20110719153543gitd39221e.noarch
aeolus-all-0.3.0-0.el6.20110719153543gitd39221e.noarch
aeolus-conductor-daemons-0.3.0-0.el6.20110719153543gitd39221e.noarch
aeolus-configure-2.0.1-1.el6.20110719144238git5ffa131.noarch
aeolus-conductor-doc-0.3.0-0.el6.20110719153543gitd39221e.noarch

Comment 1 Dave Johnson 2011-07-20 19:44:49 UTC

Created attachment 514076 [details]
useless error

it tells you that it failed to deploy but no reason why

Comment 2 wes hayutin 2011-08-30 20:05:05 UTC

*** Bug 725671 has been marked as a duplicate of this bug. ***

Comment 3 wes hayutin 2011-09-28 16:39:19 UTC

making sure all the bugs are at the right version for future queries

Comment 5 Dave Johnson 2011-11-03 19:00:26 UTC

UI still fails to check this before sending it to deltacloud which blows up with the following trace:

malformed format string - %A
/usr/lib/ruby/gems/1.8/gems/deltacloud-client-0.4.0/lib/deltacloud.rb:403:in `handle_backend_error'
/usr/lib/ruby/gems/1.8/gems/deltacloud-client-0.4.0/lib/deltacloud.rb:361:in `request'
/usr/lib/ruby/gems/1.8/gems/rest-client-1.6.1/lib/restclient/request.rb:218:in `call'
/usr/lib/ruby/gems/1.8/gems/rest-client-1.6.1/lib/restclient/request.rb:218:in `process_result'
/usr/lib/ruby/gems/1.8/gems/rest-client-1.6.1/lib/restclient/request.rb:169:in `transmit'
/usr/lib/ruby/1.8/net/http.rb:543:in `start'

Comment 6 Jan Provaznik 2012-01-03 15:55:08 UTC

fixed in commit 46ac73ebfa6e21b29b9960cf9c840c96d54f6e7d

note that architecture check is not done for imported images because it's not possible to get architecture for them.

Comment 7 Shveta 2012-01-10 09:32:40 UTC

Building and pushing for F15 i386 failed with the below error .
Not sure if it is because of hwp1 or some other reason.Nothing significant in log ..


==================================================================
 tail -f /var/log/imagefactory.log 
2012-01-10 03:35:32,524 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Waiting for EC2 ssh access: 170/300
2012-01-10 03:37:23,702 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Waiting for EC2 ssh access: 180/300
2012-01-10 03:39:14,956 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Waiting for EC2 ssh access: 190/300
|
|
|
2012-01-10 03:52:13,381 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Waiting for EC2 ssh access: 260/300
2012-01-10 03:54:04,513 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Waiting for EC2 ssh access: 270/300
2012-01-10 03:55:55,688 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Waiting for EC2 ssh access: 280/300
2012-01-10 03:57:46,908 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Waiting for EC2 ssh access: 290/300
2012-01-10 03:59:38,064 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Terminating EC2 instance and deleting temp security group
2012-01-10 03:59:38,982 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Instance status (shutting-down) - waiting for 'terminated'. [0 of 300 seconds elapsed]
2012-01-10 03:59:44,142 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Instance status (shutting-down) - waiting for 'terminated'. [5 of 300 seconds elapsed]
2012-01-10 03:59:49,309 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Instance status (shutting-down) - waiting for 'terminated'. [10 of 300 seconds elapsed]
2012-01-10 03:59:54,471 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Instance status (shutting-down) - waiting for 'terminated'. [15 of 300 seconds elapsed]
2012-01-10 03:59:59,655 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Instance status (shutting-down) - waiting for 'terminated'. [20 of 300 seconds elapsed]
2012-01-10 04:00:04,826 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Instance status (shutting-down) - waiting for 'terminated'. [25 of 300 seconds elapsed]
2012-01-10 04:00:10,034 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Instance status (shutting-down) - waiting for 'terminated'. [30 of 300 seconds elapsed]
2012-01-10 04:00:15,221 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Instance status (shutting-down) - waiting for 'terminated'. [35 of 300 seconds elapsed]
2012-01-10 04:00:20,392 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Instance status (shutting-down) - waiting for 'terminated'. [40 of 300 seconds elapsed]
2012-01-10 04:00:25,555 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Instance status (shutting-down) - waiting for 'terminated'. [45 of 300 seconds elapsed]
2012-01-10 04:00:31,037 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Removed temporary security group (imagefactory-8f8d84e5-893d-455c-a3e8-38c3325d2d43)
2012-01-10 04:00:31,037 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Exception caught in ImageFactory
2012-01-10 04:00:31,051 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder pid(7973) Message: Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/imgfac/builders/Fedora_ec2_Builder.py", line 443, in push_image
    credentials)
  File "/usr/lib/python2.6/site-packages/imgfac/builders/Fedora_ec2_Builder.py", line 614, in push_image_snapshot_ec2
    self.wait_for_ec2_ssh_access(guestaddr)
  File "/usr/lib/python2.6/site-packages/imgfac/builders/Fedora_ec2_Builder.py", line 468, in wait_for_ec2_ssh_access
    raise ImageFactoryException("Unable to gain ssh access after 300 seconds - aborting")
ImageFactoryException: Unable to gain ssh access after 300 seconds - aborting

2012-01-10 04:00:31,052 DEBUG imgfac.BuildJob.BuildJob pid(7973) Message: Builder (8f8d84e5-893d-455c-a3e8-38c3325d2d43) changed status from PUSHING to FAILED
================================

rpm -qa|grep aeolus
aeolus-configure-2.6.0-0.20120105171403gitf0043e8.el6.noarch
aeolus-conductor-doc-0.9.0-0.20120105223209git5e068fe.el6.noarch
rubygem-arel-2.0.10-0.aeolus.el6.noarch
rubygem-rack-mount-0.7.1-3.aeolus.el6.noarch
rubygem-ZenTest-4.3.3-2.aeolus.el6.noarch
rubygem-aeolus-image-0.4.0-0.20120105171419git8108b42.el6.noarch
aeolus-conductor-0.9.0-0.20120105223209git5e068fe.el6.noarch
aeolus-all-0.9.0-0.20120105223209git5e068fe.el6.noarch
rubygem-aeolus-cli-0.4.0-0.20120105171410git2c6b457.el6.noarch
aeolus-conductor-daemons-0.9.0-0.20120105223209git5e068fe.el6.noarch

Comment 8 Steve Linabery 2012-01-10 18:12:46 UTC

46ac73ebfa6e21b29b9960cf9c840c96d54f6e7d in aeolus-conductor-0.8.0-2.el6.src.rpm

Comment 9 Shveta 2012-01-16 13:37:55 UTC

Building and Pushing with F15 i386 succeeded.
Launched an instance with it for hwp1

It came up fine but with x86_64 architecture.

Is this the expected behaviour ? 

==========================================================

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

Comment 11 Rehana 2012-02-27 09:33:17 UTC

verified this bug for the images build and pushed from conductor:

Steps:
1.build and pushed a fedora 15,32 bit image to ec2
2.created a deployable of this image on x86_64 platform
3.Launched an instance using the deployable
4.Got the error message on UI, before the instance launch(attached screen shot)


[root@intel-d3c69-01 test]# rpm -qa | grep aeolus
aeolus-conductor-0.8.0-36.el6.noarch
aeolus-conductor-daemons-0.8.0-36.el6.noarch
rubygem-aeolus-image-0.3.0-10.el6.noarch
rubygem-aeolus-cli-0.3.0-10.el6.noarch
aeolus-all-0.8.0-36.el6.noarch
aeolus-conductor-doc-0.8.0-36.el6.noarch
aeolus-configure-2.5.0-15.el6.noarch

[root@intel-d3c69-01 test]# rpm -qa | grep delta*
deltacloud-core-rhevm-0.5.0-5.el6.noarch
deltacloud-core-0.5.0-5.el6.noarch
rubygem-deltacloud-client-0.5.0-2.el6.noarch
deltacloud-core-ec2-0.5.0-5.el6.noarch
deltacloud-core-vsphere-0.5.0-5.el6.noarch


Note:
please refer the bug https://bugzilla.redhat.com/show_bug.cgi?id=795743 for the architecture verification on an imported image

Comment 12 Rehana 2012-02-27 09:33:56 UTC

Created attachment 565993 [details]
error Screenshot

Comment 13 errata-xmlrpc 2012-05-15 21:48:13 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0583.html