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
making sure all the bugs are at the right version for future queries
Patch sent to the list: https://fedorahosted.org/pipermail/aeolus-devel/2011-December/007588.html
Fixed in commit: f1e6529a90836da339d053a0299db074085e8228
"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
Created attachment 550236 [details] launch button
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