Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Configure aeolus for ec2 and mock 2. Cloud--> Component Outline --> Import an ec2 image 3. New deployable from component outline , launch button will be greyed out 3. since there is no build for mock take another route to deployable Content --> Default catalog --> deployable Launch button is enabled Actual results: Expected results: Additional info: rpm -qa|grep aeolus aeolus-conductor-doc-0.8.0-23.el6.noarch aeolus-configure-2.5.0-12.el6.noarch aeolus-conductor-daemons-0.8.0-23.el6.noarch rubygem-aeolus-image-0.3.0-7.el6.noarch rubygem-aeolus-cli-0.3.0-8.el6.noarch aeolus-conductor-0.8.0-23.el6.noarch aeolus-all-0.8.0-23.el6.noarch
moving version to 1.0.0 . version = found in version
I can't reproduce this. If I follow the Steps to Reproduce, I can launch the image successfully. It may have been fixed in the past couple weeks. Is this still happening?
This seems to have been fixed in last few builds. Can't reproduce the bug again. Verifying it rpm -qa|grep aeolus aeolus-conductor-0.8.0-36.el6.noarch rubygem-aeolus-cli-0.3.0-10.el6.noarch aeolus-conductor-daemons-0.8.0-36.el6.noarch aeolus-configure-2.5.0-15.el6.noarch rubygem-aeolus-image-0.3.0-10.el6.noarch aeolus-all-0.8.0-36.el6.noarch aeolus-conductor-doc-0.8.0-36.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