Bug 726144

Summary: multi-target build, immediate ec2 push shows image already pushed
Product: [Retired] CloudForms Cloud Engine Reporter: Dave Johnson <dajohnso>
Component: rubygem-aeolus-imageAssignee: Martyn Taylor <mtaylor>
Status: CLOSED ERRATA QA Contact: Dave Johnson <dajohnso>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, cpelland, dajohnso, morazi, ssachdev, whayutin
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-05-15 19:40:58 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-27 16:39:32 UTC
Description of problem:
===============================================
NOTE: This is most likely related to bug 725932...

If I build a image for ec2 and one of the private cloud vendors, ec2 finishes immediately find the pre-canned jeos images already in the ec2 cloud.  when I go to push the ec2 image (while the other image is still being built), aeolus-image returns with 'the image has already been pushed, use --build' even though it has not.



[root@ibm-x3650-04 ~]# aeolus-image build --template vmware-rhel-install-cmake-pkg-template.tpl --target vsphere,ec2

Target Image: 716eab46-63a0-4093-93d9-066285b240a4
Image: 4d24a5b3-5c7d-446f-9b22-b76e0037bbc3
Build: 8ba5cbeb-b06c-43f2-9da1-20993d240337
Status: BUILDING
Percent Complete: 0

Target Image: ea621bf7-2ca7-4ba8-9d6b-74a914db7a8b
Image: 4d24a5b3-5c7d-446f-9b22-b76e0037bbc3
Build: 8ba5cbeb-b06c-43f2-9da1-20993d240337
Status: New
Percent Complete: 0

*** immediate push while vsphere is still building ***
[root@ibm-x3650-04 ~]# aeolus-image push --id 4d24a5b3-5c7d-446f-9b22-b76e0037bbc3 --provider ec2-us-west-1,ec2-us-east-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>

<vsphere build completes>

*** successful push using the image id ***
[root@ibm-x3650-04 ~]# aeolus-image push --id 4d24a5b3-5c7d-446f-9b22-b76e0037bbc3 --provider ec2-us-west-1,ec2-us-east-1

Provider Image: 2854f78a-6999-4855-87a8-a2bed0af4b6e
Image: 4d24a5b3-5c7d-446f-9b22-b76e0037bbc3
Build: 8ba5cbeb-b06c-43f2-9da1-20993d240337
Status: PUSHING
Percent Complete: 0

Provider Image: b7cc415b-6f15-4f9f-9797-5451b6fc2620
Image: 4d24a5b3-5c7d-446f-9b22-b76e0037bbc3
Build: 8ba5cbeb-b06c-43f2-9da1-20993d240337
Status: PUSHING
Percent Complete: 0
[root@ibm-x3650-04 ~]#

Comment 1 Jason Guiditta 2011-07-27 17:17:24 UTC
Since Martyn is most familiar with this part of code, reassigning to him, I'll help if needed.

Comment 2 Martyn Taylor 2011-09-06 09:58:30 UTC
This looks more like a incorrect error message, rather than a logic bug.  We have to wait for all target images to complete building before we can push the image.  I'll investigate further and send a patch to the list.

Comment 3 wes hayutin 2011-09-28 16:37:38 UTC
making sure all the bugs are at the right version for future queries

Comment 5 Martyn Taylor 2011-10-06 12:29:23 UTC
I had a patch on the list for this but it seems to have gotten missed.  Regardless this should go away in the next release of aeolus-image

Comment 6 Aziza Karol 2011-11-23 06:32:52 UTC
Recreated the above steps.
For immediate ec2 push, this error is not displayed now.

[root@ibm-x3620m3-01 rheltempwes]# aeolus-cli build --target ec2,vsphere --template RHEL61.tpl 
Image: 409a42c6-4792-43cc-9226-bef149ae12f9
Build: 0811da57-afd4-414a-b4b0-45f6086fa6ef
Target Image: a0f042e7-1e21-4e39-bc97-22eb509d169f	 :Status COMPLETED
Target Image: 3af1da7e-3695-466f-b5ed-e55b16cba5c5	 :Status BUILDING

*** immediate push while vsphere is still building ***

[root@ibm-x3620m3-01 rheltempwes]# aeolus-cli push --account aziza_east,aziza_west --image 409a42c6-4792-43cc-9226-bef149ae12f9
Image: 409a42c6-4792-43cc-9226-bef149ae12f9
Provider Image: 83b15dea-e383-4fc9-9ffc-6d225d523c56	 Status: PUSHING
Provider Image: 207888b3-cb88-4a85-b149-cb0383238ddc	 Status: PUSHING


verified on:
[root@ibm-x3620m3-01 ~]# rpm -qa | egrep 'aeolus|iwhd|imagefactory'
iwhd-1.0-1.fc15.x86_64
aeolus-conductor-0.7.0-0.20111122193230git4823c2b.fc15.noarch
imagefactory-jeosconf-ec2-rhel-0.8.9-1.fc15.noarch
rubygem-aeolus-cli-0.1.0-4.fc15.noarch
rubygem-aeolus-image-0.1.0-6.fc15.noarch
aeolus-conductor-doc-0.7.0-0.20111122193230git4823c2b.fc15.noarch
imagefactory-jeosconf-ec2-fedora-0.8.9-1.fc15.noarch
aeolus-conductor-daemons-0.7.0-0.20111122193230git4823c2b.fc15.noarch
aeolus-configure-2.4.0-0.20111118150133gitde3c009.fc15.noarch
imagefactory-0.8.9-1.fc15.noarch
aeolus-all-0.7.0-0.20111122193230git4823c2b.fc15.noarch
rubygem-imagefactory-console-0.5.0-4.20110824113238gitd9debef.fc15.noarch

Comment 8 errata-xmlrpc 2012-05-15 19:40:58 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