Red Hat Bugzilla – Bug 864457
conductor prefers the provider accounts defined with the highest priority value, instead of lowest
Last modified: 2012-10-23 11:01:15 EDT
Description of problem:
when launching an application, if conductor is let to choose the provider to be used, it prefers the provider account defined with the highest number in the priority field, instead of the lowest, as assumed by the user guide.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. configure at least two different provider accounts and set two different priority values (say 1 and 2)
2. launch an application letting conductor to auto-select the target cluster
3. observe conductor preferring the account with the highest value set
this has to be updated in the doc, not in the software, as per bug
The provider selection during deployment launch has changed a lot since 1.0. In 1.1 we are randomly picking from the set of available provider accounts. The priority attribute is only used for the weight of the random selection.
So you cannot conclude that the provider account with the higher priority will be selected, or the one with the lower priority. Since it's based on random selection it can happen either way.