Bug 854882 - Unable to remove provider account from the priority group of Strict Order Strategy
Summary: Unable to remove provider account from the priority group of Strict Order Str...
Keywords:
Status: CLOSED EOL
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-06 08:31 UTC by Rehana
Modified: 2020-03-27 19:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:36:58 UTC
Embargoed:

Attachments (Terms of Use)

Description Rehana 2012-09-06 08:31:36 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.Login to conductor
2.Add priority group with two provider accounts (say ec2-us-west-1  and rhevm)
3.launch instances
4.Now remove provider "ec2-us-west-1" from the priority group
  
Actual results:
Observed that the provider account was not getting removed from priority group

Expected results:
User should be allowed to modify(add/remove)the provider account from the priority group 

Additional info:
rpm -qa | grep aeolus 
aeolus-conductor-0.13.0-0.20120906030013git8112e57.fc16.noarch
aeolus-conductor-doc-0.13.0-0.20120906030013git8112e57.fc16.noarch
aeolus-configure-2.8.0-0.20120905230028gitb24d837.fc16.noarch
aeolus-conductor-daemons-0.13.0-0.20120906030013git8112e57.fc16.noarch
aeolus-all-0.13.0-0.20120906030013git8112e57.fc16.noarch
rubygem-aeolus-image-0.6.0-0.20120905230033git902c81c.fc16.noarch
rubygem-aeolus-cli-0.7.0-0.20120905230030gitd64d64f.fc16.noarch
Note You need to log in before you can comment on or make changes to this bug.