Bug 785198
| Summary: | conductor/catalogs/1/deployables/ shows ec2 outlines as not built when in fact they are | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | wes hayutin <whayutin> | ||||||||
| Component: | aeolus-conductor | Assignee: | Matt Wagner <matt.wagner> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | wes hayutin <whayutin> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 1.0.0 | CC: | akarol, athomas, deltacloud-maint, ssachdev | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| URL: | https://qeblade30.rhq.lab.eng.bos.redhat.com/conductor/catalogs/1/deployables/4 | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-08-30 17:14:36 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 557885 [details]
ss2
pretty sure the build was kicked off via the webui. I can try to recreate if needed. 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. 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) 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) 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
Created attachment 561551 [details]
built
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 |
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..