Hide Forgot
Description of problem: recreate: 1. import an ec2 ami 2. create a deployable def, in this definition use a hwp that does not exist in the system 3. launch the deployable... launch validations fails and user is prompted w/ an error.. could not launch. A deployment is still created in the ui.. that should not be the case[root@unused ~]# rpm -qa | grep aeolus aeolus-conductor-doc-0.4.0-0.20110922165939git5b371be.fc15.noarch aeolus-conductor-0.4.0-0.20110922165939git5b371be.fc15.noarch aeolus-conductor-daemons-0.4.0-0.20110922165939git5b371be.fc15.noarch aeolus-all-0.4.0-0.20110922165939git5b371be.fc15.noarch aeolus-conductor-devel-0.4.0-0.20110922165939git5b371be.fc15.noarch aeolus-configure-2.0.2-4.20110921102958gitcaa9608.fc15.noarch rubygem-aeolus-image-0.1.0-3.20110922120732gita0b9a44.fc15.noarch [root@unused ~]#
making sure all the bugs are at the right version for future queries
import vs build ec2 images is not important here.. just make sure you get a failed deployment
The patch is on the list: https://fedorahosted.org/pipermail/aeolus-devel/2011-November/006639.html
removing bugs from ce-sprint from the tracker.. you can find these bugs by querying the "qa whiteboard" for ce-sprint-60
Fixed in commit: f1e6529a90836da339d053a0299db074085e8228
Launch button is disabled if deployable xml is made with not existing hwp. "frontend: Hardware profile hwp2 specified in XML doesn't exist." rpm -qa|grep aeolus aeolus-conductor-doc-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-configure-2.5.0-0.20111222173430git17b704a.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-conductor-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-conductor-daemons-0.8.0-0.20111222233342gitd98cb57.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