Bug 796190 - Priority of provider account is not considered when launching with "Auto-select"
Summary: Priority of provider account is not considered when launching with "Auto-select"
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-22 12:59 UTC by Shveta
Modified: 2012-02-22 13:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-22 13:19:48 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Shveta 2012-02-22 12:59:54 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Created ec2 account with priority 1 and vsphere account with priority 2
2. Launched instance (built and pushed for both) with "Auto-select" in cluster 
3. instance was launched for ec2 .. correct

then i edited accounts and interchanged priorities 
i.e 1 for vsphere and 2 for ec2 and launched with "Auto select"

instance was launched for ec2 
  
Actual results:


Expected results:


Additional info:

rpm -qa|grep aeolus
aeolus-conductor-daemons-0.8.0-33.el6.noarch
aeolus-configure-2.5.0-14.el6.noarch
rubygem-aeolus-image-0.3.0-8.el6.noarch
aeolus-conductor-0.8.0-33.el6.noarch
rubygem-aeolus-cli-0.3.0-9.el6.noarch
aeolus-conductor-doc-0.8.0-33.el6.noarch
aeolus-all-0.8.0-33.el6.noarch
Comment 1 Shveta 2012-02-22 13:19:48 UTC 
The profile matching to vsphere was not there , closing the bug
Note You need to log in before you can comment on or make changes to this bug.