Bug 773410

Summary: provider priority is not taken into account when launching instances w/ Realm w/ multiple realms(datastores)
Product: [Retired] CloudForms Cloud Engine Reporter: wes hayutin <whayutin>
Component: aeolus-conductorAssignee: Shveta <ssachdev>
Status: CLOSED ERRATA QA Contact: wes hayutin <whayutin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, deltacloud-maint, ssachdev
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-15 21:39:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
ss1
none
ss2
none
common
none
common none

Description wes hayutin 2012-01-11 18:55:15 UTC 
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
Comment 1 wes hayutin 2012-01-11 18:56:27 UTC 
Created attachment 552196 [details]
ss1
Comment 2 wes hayutin 2012-01-11 18:57:25 UTC 
Created attachment 552197 [details]
ss2
Comment 3 wes hayutin 2012-01-12 16:31:56 UTC 
adding to ce-sprint
Comment 4 wes hayutin 2012-01-12 16:39:03 UTC 
removing ce-sprint-next tracker
Comment 5 Shveta 2012-01-13 09:07:51 UTC 
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
Comment 6 wes hayutin 2012-01-24 16:54:25 UTC 
need to retest
Comment 8 Shveta 2012-02-24 12:14:22 UTC 
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
Comment 9 Shveta 2012-02-24 12:15:42 UTC 
Created attachment 565589 [details]
common
Comment 10 errata-xmlrpc 2012-05-15 21:39:31 UTC 
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