Hide Forgot
Description of problem: recreate: 1. vsphere provider account, priority =1 2. rhevm provider account, priority =2 3. realm (called both-realms) w/ rhevm and vsphere realms lists (see screenshot) 4. launch instance into realm called (both-realms) 5. instances is launched into rhevm the priority would indicate it should launch into vsphere.. I thought See screenshot [root@qeblade32 yum.repos.d]# rpm -qa | grep aeolus aeolus-configure-2.5.0-3.el6.noarch rubygem-aeolus-image-0.3.0-2.el6.noarch aeolus-conductor-0.8.0-5.el6.noarch rubygem-aeolus-cli-0.3.0-3.el6.noarch aeolus-conductor-doc-0.8.0-5.el6.noarch aeolus-conductor-daemons-0.8.0-5.el6.noarch aeolus-all-0.8.0-5.el6.noarch
Created attachment 552196 [details] ss1
Created attachment 552197 [details] ss2
adding to ce-sprint
removing ce-sprint-next tracker
Tried to recreate this bug but could not 1) Vsphere with priority 1 2) Rhev with priority 2 3) realm mapped to both vpshere and RHEV 4) Launched instance for common realm 5) Instance was launched for Vsphere (with priority 1) rpm -qa|grep aeolus aeolus-conductor-0.8.0-5.el6.noarch aeolus-configure-2.5.0-4.el6.noarch aeolus-conductor-doc-0.8.0-5.el6.noarch aeolus-all-0.8.0-5.el6.noarch rubygem-aeolus-cli-0.3.0-3.el6.noarch rubygem-aeolus-image-0.3.0-2.el6.noarch aeolus-conductor-daemons-0.8.0-5.el6.noarch
need to retest
Created attachment 565588 [details] common 1) Vsphere with priority 1 2) Rhev with priority 2 3) realm mapped to both vpshere and RHEV 4) Launched instance for common realm 5) Instance was launched for Vsphere (with priority 1) rpm -qa|grep aeolus aeolus-conductor-0.8.0-35.el6.noarch rubygem-aeolus-cli-0.3.0-10.el6.noarch aeolus-conductor-doc-0.8.0-35.el6.noarch rubygem-aeolus-image-0.3.0-9.el6.noarch aeolus-all-0.8.0-35.el6.noarch aeolus-conductor-daemons-0.8.0-35.el6.noarch aeolus-configure-2.5.0-15.el6.noarch
Created attachment 565589 [details] common
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