yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #28446
[Bug 1394551] Re: Legacy GroupAffinity and GroupAntiAffinity filters are broken
looks like this is fixed
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1394551
Title:
Legacy GroupAffinity and GroupAntiAffinity filters are broken
Status in OpenStack Compute (Nova):
Invalid
Status in OpenStack Compute (nova) juno series:
Fix Released
Bug description:
Both GroupAffinity and GroupAntiAffinity filters are broken. The
scheduler does not respect the filters and schedules the servers
against the policy.
Reproduction steps:
0) Spin up a single node devstack
1) Add GroupAntiAffinityFilter to scheduler_default_filters in nova.conf and restart the nova services
2) Boot multiple server with the following command
nova boot --image cirros-0.3.2-x86_64-uec --flavor 42 --hint group=foo server-1
Expected behaviour:
The second and any further boot should fail with NoValidHostFound exception as anti-affinity policy cannot be fulfilled.
Actual behaviour:
Any number of servers are booted to the same compute node
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1394551/+subscriptions
References