Bug 723586

Summary: blank image id when pushing a build
Product: [Retired] CloudForms Cloud Engine Reporter: Dave Johnson <dajohnso>
Component: rubygem-aeolus-imageAssignee: Martyn Taylor <mtaylor>
Status: CLOSED ERRATA QA Contact: wes hayutin <whayutin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, cpelland, dajohnso, 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 19:40:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dave Johnson 2011-07-20 16:15:25 UTC
Description of problem:
-----------------------
So I built a image and pushed it to ec2-east.  I then wanted to push it to ec2-west but aeolus-image returned:

   [root@hp-dc5800-01 ~]# aeolus-image push --id f1fb52c8-b8c5-4942-9def- 
     6e1409db2424 --provider ec2-us-west-1
   
   ERROR: This image has already been pushed, to push to another provider
   please push via build-id rather than image-id e.g. aeolus-image push 
   --provider <provider> --build <build-id>

So I did as instructed and got a blank image id, as follows:
   
   [root@hp-dc5800-01 ~]# aeolus-image push --build a1f57e76-019b-
     4995-a175-03b78d7e62b9 --provider ec2-us-west-1

   Provider Image: 00549100-d637-4b49-9a39-04f27b35aa45
   Image: 
   Build: a1f57e76-019b-4995-a175-03b78d7e62b9
   Status: PUSHING
   Percent Complete: 0

Since a deployable xml needs a image id and a build id, I am thinking that by leaving the image id out, that will spawn some confusion for the customer.  I successfully used the image id from the initial push command and was successful in deploying the image to ec2-west. 


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

Comment 1 wes hayutin 2011-09-28 16:36:59 UTC
making sure all the bugs are at the right version for future queries

Comment 3 Aziza Karol 2011-11-21 07:48:25 UTC
No such error displayed and also image id is not blank while pushing.

[root@dell-pem710-01 templates]#  aeolus-cli build --target ec2 --template fedora15.tpl 
Image: ce9b2c81-4f32-4a45-b63f-f054db1dfb2e
Build: 3b87e0d6-93e7-4de4-9860-3fcdf30c24ad
Target Image: 2d7af01e-0146-4f75-a758-388695282b16	 :Status New

[root@dell-pem710-01 templates]#  aeolus-cli push --account aziza_west --image ce9b2c81-4f32-4a45-b63f-f054db1dfb2e
Image: ce9b2c81-4f32-4a45-b63f-f054db1dfb2e
Provider Image: 18c09d9b-5b98-4424-a19d-5bbe1e32607f	 Status: New

verified on:
[root@dell-pem710-01 ~]# rpm -qa | grep aeolus
rubygem-rack-mount-0.7.1-3.aeolus.el6.noarch
aeolus-conductor-doc-0.7.0-0.20111118205914git4c5036a.el6.noarch
rubygem-aeolus-cli-0.1.0-4.el6.noarch
rubygem-arel-2.0.10-0.aeolus.el6.noarch
rubygem-aeolus-image-0.1.0-6.el6.noarch
aeolus-configure-2.4.0-0.20111118150133gitde3c009.el6.noarch
aeolus-all-0.7.0-0.20111118205914git4c5036a.el6.noarch
aeolus-conductor-0.7.0-0.20111118205914git4c5036a.el6.noarch
rubygem-ZenTest-4.3.3-2.aeolus.el6.noarch
aeolus-conductor-daemons-0.7.0-0.20111118205914git4c5036a.el6.noarch

Comment 5 errata-xmlrpc 2012-05-15 19:40:39 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-0592.html