Bug 725932 - multi-target builds cause blanks for latest push build
Summary: multi-target builds cause blanks for latest push build
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: rubygem-aeolus-image
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Martyn Taylor
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-27 02:54 UTC by Dave Johnson
Modified: 2012-05-15 19:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-15 19:40:54 UTC


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0592 0 normal SHIPPED_LIVE new packages: rubygem-aeolus-image 2012-05-15 22:31:14 UTC

Description Dave Johnson 2011-07-27 02:54:23 UTC
Description of problem:
=========================
If you run a aeolus-image build for multiple targets, then begin pushing them, and run 'aeolus-image list --images' after its all said and done, you will get blanks (no build id) in the 'latest pushed build' column.  Seems to work fine when building for a single target.


Version-Release number of selected component (if applicable):
==============================================================
rubygem-aeolus-image-0.0.1-3.el6.noarch


Steps to Reproduce:
======================
1. aeolus-image build --template /root/vmware-rhel-install-cmake-pkg-template.tpl --target ec2,vsphere
2. aeolus-image push --id 83742a29-c105-4a9a-bf16-69b501111639 --provider ec2-us-east-1,vsphere
3.aeolus-image list --images

IMAGE ID                                 LASTEST PUSHED BUILD                     NAME               TARGET      OS         OS VERSION     ARCH       DESCRIPTION
83742a29-c105-4a9a-bf16-69b501111639                                              rhel6_1_x86_64     ec2         RHEL-6     1              x86_64     rhel 6.1 x86_64 template
83742a29-c105-4a9a-bf16-69b501111639                                              rhel6_1_x86_64     vsphere     RHEL-6     1              x86_64     rhel 6.1 x86_64 template

Comment 1 Dave Johnson 2011-07-27 16:40:16 UTC
most likely related to bug 726144

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

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

Comment 5 Martyn Taylor 2011-10-06 12:26:52 UTC
This is a result of the hackery around iwhd to get image status and will go away in the next version of aeolus-image when we update it to speak directly to conductor Image Management API

Comment 6 Aziza Karol 2011-11-23 07:18:30 UTC
latest push build column is removed.

aeolus-cli list --images does not list latest push build column now.

root@ibm-x3620m3-01 rheltempwes]# aeolus-cli  list --images
ID                                       Name               OS         OS Version     Arch       Description        
------------------------------------     --------------     ------     ----------     ------     --------------     
409a42c6-4792-43cc-9226-bef149ae12f9     RHEL_westest01     RHEL-6     1              x86_64     RHEL61 x86_64      

[root@ibm-x3620m3-01 ~]# rpm -qa | grep aeolus
aeolus-conductor-0.7.0-0.20111122193230git4823c2b.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
aeolus-conductor-daemons-0.7.0-0.20111122193230git4823c2b.fc15.noarch
aeolus-configure-2.4.0-0.20111118150133gitde3c009.fc15.noarch
aeolus-all-0.7.0-0.20111122193230git4823c2b.fc15.noarch

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


Note You need to log in before you can comment on or make changes to this bug.