| Summary: | disable "launch" button if no images are built/pushed | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | wes hayutin <whayutin> | ||||||||||||
| Component: | aeolus-conductor | Assignee: | Scott Seago <sseago> | ||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | wes hayutin <whayutin> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 1.0.0 | CC: | akarol, deltacloud-maint, slinaber, ssachdev, sseago | ||||||||||||
| Target Milestone: | rc | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | Unspecified | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| URL: | https://brewweb.devel.redhat.com/buildinfo?buildID=194749 | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2012-05-15 21:33:42 UTC | Type: | --- | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
wes hayutin
2012-01-10 15:55:58 UTC
Created attachment 551875 [details]
ss1
Created attachment 551876 [details]
ss2
Created attachment 551877 [details]
ss3
Created attachment 551878 [details]
ss4
Actually, 'images ready' is a misnomer, what that really means is 'images valid' -- i.e. the referenced image exists in IWHD, if images aren't "ready" in this sense, the user has to edit the deployable XML to provide a valid image UUID. So we should really change 'images ready' to 'images valid' -- i.e. if images aren't ready/valid, we can't even build -- we have to fix the deployable. Once images are valid, we can build/push. So I'd change 2) in the above problem description to show this as 'images are valid' -- since that's the output of Deployable XML validation rather than image build status -- image build status (i.e. ready vs. not) is in the per-provider-account status fields. The need to disable the 'launch' button is, of course, still a valid problem. adding to ce-sprint removing ce-sprint-next tracker Patch here: https://fedorahosted.org/pipermail/aeolus-devel/2012-January/008065.html 'images ready' is now 'images valid', and launch button is disabled unless all images are pushed to at least one provider account. *** Bug 770091 has been marked as a duplicate of this bug. *** d24dcbe780e127a7054cc10187df0b0f3e93198a in aeolus-conductor-0.8.0-8.el6.src.rpm Created attachment 556219 [details]
disabled_launch_btn
"Image Ready" is replaced by "Image Valid" Launch button is disabled if images are not built and pushed. Verified in rpm -qa|grep aeolus aeolus-conductor-0.8.0-8.el6.noarch aeolus-conductor-daemons-0.8.0-8.el6.noarch rubygem-aeolus-image-0.3.0-3.el6.noarch rubygem-aeolus-cli-0.3.0-4.el6.noarch aeolus-all-0.8.0-8.el6.noarch aeolus-configure-2.5.0-5.el6.noarch aeolus-conductor-doc-0.8.0-8.el6.noarch 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-0583.html |