Bug 723686

Summary: launch this deployment should grey out if deployable xml error detected
Product: [Retired] CloudForms Cloud Engine Reporter: Dave Johnson <dajohnso>
Component: aeolus-conductorAssignee: Tomas Sedovic <tsedovic>
Status: CLOSED ERRATA QA Contact: Dave Johnson <dajohnso>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, cpelland, dajohnso, deltacloud-maint, ssachdev, whayutin
Target Milestone: beta   
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 21:50:26 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 Flags
launch button none

Description Dave Johnson 2011-07-20 19:39:07 UTC 
Description of problem:
=============================
If you add a deployable when the build/image id or the hwp doesn't exist, an error is given in the UI but the 'launch this deployment' button is still enabled.  Clicking it creates a deployment without any instances.  This button should be inactive when errors are detected.

Version-Release number of selected component (if applicable):
=====================================================================
[root@ibm-x3650-04 ~]# rpm -qa | grep aeolus
rubygem-aeolus-image-0.0.1-1.el6.20110719153543gitd39221e.noarch
aeolus-conductor-0.3.0-0.el6.20110719153543gitd39221e.noarch
aeolus-all-0.3.0-0.el6.20110719153543gitd39221e.noarch
aeolus-conductor-daemons-0.3.0-0.el6.20110719153543gitd39221e.noarch
aeolus-configure-2.0.1-1.el6.20110719144238git5ffa131.noarch
Comment 1 wes hayutin 2011-09-28 16:38:48 UTC 
making sure all the bugs are at the right version for future queries
Comment 3 Tomas Sedovic 2011-12-21 09:33:28 UTC 
Patch sent to the list: https://fedorahosted.org/pipermail/aeolus-devel/2011-December/007588.html
Comment 4 Tomas Sedovic 2011-12-21 16:29:03 UTC 
Fixed in commit: f1e6529a90836da339d053a0299db074085e8228
Comment 5 Aziza Karol 2012-01-02 10:58:54 UTC 
"Launch" deployment button is disabled when the build/image id or the hwp doesn't exist in the deployable.

Also an error message "No image build was found with uuid and no image was found with uuid" is displayed.

see attached screen shot.

verified on:
[root@dell-pe1950-01 ~]# rpm  -qa | grep aeolus
aeolus-conductor-daemons-0.8.0-0.20111222233342gitd98cb57.el6.noarch
rubygem-aeolus-image-0.3.0-0.20111222173411gitc13b654.el6.noarch
rubygem-aeolus-cli-0.3.0-0.20111222173356git3cd6277.el6.noarch
aeolus-all-0.8.0-0.20111222233342gitd98cb57.el6.noarch
aeolus-configure-2.5.0-0.20111222173430git17b704a.el6.noarch
aeolus-conductor-0.8.0-0.20111222233342gitd98cb57.el6.noarch
aeolus-conductor-doc-0.8.0-0.20111222233342gitd98cb57.el6.noarch
Comment 6 Aziza Karol 2012-01-02 10:59:26 UTC 
Created attachment 550236 [details]
launch button
Comment 8 errata-xmlrpc 2012-05-15 21:50:26 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-0583.html