Hide Forgot
Description of problem: ============================= Summary pretty much says it all. After turning the rhevm provider off, I can still deploy images through conductor that start on the rhevm server. This is not the case with vsphere. vsphere does not allow deployments when the provider is turned off. Not sure about ec2, experiencing some unrelated push/deploy issues that are blocking testing this. Version-Release number of selected component (if applicable): ================================================================= aeolus-all-0.4.0-0.20111005143854git16fdbbd.fc15.noarch aeolus-conductor-0.4.0-0.20111005143854git16fdbbd.fc15.noarch aeolus-conductor-daemons-0.4.0-0.20111005143854git16fdbbd.fc15.noarch aeolus-conductor-doc-0.4.0-0.20111005143854git16fdbbd.fc15.noarch aeolus-configure-2.0.2-4.20111005095819gitaf7e59a.fc15.noarch rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.fc15.noarch rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.fc15.noarch
This is working here, I suppose I need to double check f15 aeolus-all-0.5.0-0.20111007200330gite77b251.el6.noarch aeolus-conductor-0.5.0-0.20111007200330gite77b251.el6.noarch aeolus-conductor-daemons-0.5.0-0.20111007200330gite77b251.el6.noarch aeolus-conductor-doc-0.5.0-0.20111007200330gite77b251.el6.noarch aeolus-configure-2.2.0-1.20111007151942git26136f2.el6.noarch rubygem-actionmailer-3.0.9-1.aeolus.el6.noarch rubygem-actionpack-3.0.9-1.aeolus.el6.noarch rubygem-activerecord-3.0.9-1.aeolus.el6.noarch rubygem-activesupport-3.0.9-1.aeolus.el6.noarch rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.el6.noarch rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.el6.noarch rubygem-arel-2.0.10-0.aeolus.el6.noarch rubygem-rack-mount-0.7.1-3.aeolus.el6.noarch rubygem-ZenTest-4.3.3-2.aeolus.el6.noarch
Looks good on f15 as well [root@dell-pe2900-01 ~]# rpm -qa | grep aeolus | sort aeolus-all-0.5.0-0.20111007200330gite77b251.fc15.noarch aeolus-conductor-0.5.0-0.20111007200330gite77b251.fc15.noarch aeolus-conductor-daemons-0.5.0-0.20111007200330gite77b251.fc15.noarch aeolus-conductor-doc-0.5.0-0.20111007200330gite77b251.fc15.noarch aeolus-configure-2.2.0-1.20111007151942git26136f2.fc15.noarch rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.fc15.noarch rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.fc15.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