Bug 785198 - conductor/catalogs/1/deployables/ shows ec2 outlines as not built when in fact they are
Summary: conductor/catalogs/1/deployables/ shows ec2 outlines as not built when in fac...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
Assignee: Matt Wagner
QA Contact: wes hayutin
URL: https://qeblade30.rhq.lab.eng.bos.red...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-27 15:33 UTC by wes hayutin
Modified: 2014-08-17 22:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-30 17:14:36 UTC
Embargoed:


Attachments (Terms of Use)
ss1 (139.95 KB, image/png)
2012-01-27 15:33 UTC, wes hayutin
no flags Details
ss2 (121.80 KB, image/png)
2012-01-27 15:33 UTC, wes hayutin
no flags Details
built (217.22 KB, image/png)
2012-02-13 13:50 UTC, Shveta
no flags Details

Description wes hayutin 2012-01-27 15:33:05 UTC
Created attachment 557884 [details]
ss1

Description of problem:

recreate:
In my case I built for rhevm,vsphere, and ec2 at once.. but I suspect that is not needed...

build a outline for ec2..
nav to deployable page, and notice


ec2
ec2-us-east-1 | ec2East	Component Outlines are not Built


see screenshots..

Comment 1 wes hayutin 2012-01-27 15:33:39 UTC
Created attachment 557885 [details]
ss2

Comment 2 wes hayutin 2012-01-31 20:02:58 UTC
pretty sure the build was kicked off via the webui.  I can try to recreate if needed.

Comment 3 Matt Wagner 2012-02-01 16:20:59 UTC
This appears to be a bug that occurs when an image fails while building, leaving some elements but not others. We are inconsistent in how we display status in that case.

I'm going to clean that up to be consistent and display something helpful, but you obviously still have the problem that the image failed to build, which is a separate issue.

I may include a tangential fix here, where we don't build for disabled providers.

Comment 4 Matt Wagner 2012-02-01 18:25:32 UTC
Patch on list: http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-February/008556.html (there is way more to that email than the archives are showing)

Comment 5 Matt Wagner 2012-02-06 18:59:29 UTC
Re-sent after feedback: http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-February/008671.html (and this time, the mailing list didn't eat the body of my response)

Comment 6 Matt Wagner 2012-02-07 18:30:12 UTC
Pushed to staging repo this morning:

commit d574184e14600dfa4c3c34761e89d475a5905245
Author: Matt Wagner <matt.wagner>
Date:   Mon Feb 6 11:29:26 2012 -0500

    BZ 785198 - Do not show broken builds in list
    
    We need to check for the presence of @latest_build to weed out builds
    that started but subsequently failed. This brings the list of builds
    into consistency with how the deployable details page works.
    
    Resolves https://bugzilla.redhat.com/show_bug.cgi?id=785198

commit 06f49c014ffe3420ff013ad54f7a71cc8df96221
Author: Matt Wagner <matt.wagner>
Date:   Wed Feb 1 11:32:34 2012 -0500

    BZ 785198 - Do not build images for disabled providers

Comment 7 Shveta 2012-02-13 13:50:04 UTC
Created attachment 561551 [details]
built

Comment 8 Shveta 2012-02-13 13:50:38 UTC
Outlines show built status 

rpm -qa|grep aeolus
aeolus-conductor-0.8.0-25.el6.noarch
aeolus-conductor-doc-0.8.0-25.el6.noarch
rubygem-aeolus-cli-0.3.0-8.el6.noarch
aeolus-conductor-daemons-0.8.0-25.el6.noarch
aeolus-configure-2.5.0-12.el6.noarch
aeolus-all-0.8.0-25.el6.noarch
rubygem-aeolus-image-0.3.0-7.el6.noarch


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