Bug 1014948 - GroupAntiAffinityFilter filters are broken
GroupAntiAffinityFilter filters are broken
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova (Show other bugs)
All Linux
medium Severity medium
: z4
: 3.0
Assigned To: Xavier Queralt
Gabriel Szasz
: Triaged, ZStream
Depends On:
Blocks: 1039688
  Show dependency treegraph
Reported: 2013-10-03 03:47 EDT by Dharmit Shah
Modified: 2018-02-08 05:07 EST (History)
11 users (show)

See Also:
Fixed In Version: openstack-nova-2013.1.4-2.el6ost
Doc Type: Bug Fix
Doc Text:
When using GroupAntiAffinityFilter, the scheduler was not filtering instances in the group, which could cause an instance to not be scheduled at all if a group was specified on boot. With this fix, groups are taken into account and the instance is scheduled as expected.
Story Points: ---
Clone Of:
: 1039688 (view as bug list)
Last Closed: 2014-01-30 14:59:49 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1218878 None None None Never
OpenStack gerrit 55154 None None None Never

  None (edit)
Description Dharmit Shah 2013-10-03 03:47:19 EDT
Description of problem:
GroupAffinityFilter doesn't work as expected.

There's an upstream bug https://bugs.launchpad.net/nova/+bug/1218878 tracking the issue about GroupAffinityFilter and GroupAntiAffinityFilter. Commit for the same is proposed in https://github.com/openstack/nova/commit/4233e16ba2f5bb85e93494b6eeb9ffff31dbdf30

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:
Comment 1 Xavier Queralt 2013-11-06 06:23:02 EST
There is already a backport of the patch for grizzly upstream, if it gets in we'll get it in the next rebase.
Comment 2 Xavier Queralt 2013-12-02 15:22:28 EST
How to reproduce:

1. Deploy openstack with two compute nodes (compute1 and compute2).
2. Set the key 'scheduler_default_filters' in /etc/nova/nova.conf to have the following filters:
  * AvailabilityZoneFilter,RamFilter,ComputeFilter,GroupAntiAffinityFilter
3. Restart the scheduler:
  * service openstack-nova-scheduler restart
4. Start two instances, one on each compute node:
  * nova boot --image cirros --flavor m1.tiny --availability-zone nova:compute1 vm-compute1
  * nova boot --image cirros --flavor m1.tiny --availability-zone nova:compute2 vm-compute2
5. Start another instance in a group:
  * nova boot --image cirros --flavor m1.tiny --hint group=foo vm-compute
6. Without the fix the instance will move to the ERROR state and a WARNING will appear in scheduler.log.
Comment 4 Stephen Gordon 2013-12-09 14:23:25 EST
Xavier, how is group "foo" actually defined (and the policy set)? I thought the API for this didn't get accepted yet?
Comment 5 Xavier Queralt 2013-12-10 03:24:53 EST
In 3.0 only the GroupAntiAffinityFilter exists.
Comment 6 Xavier Queralt 2013-12-10 03:42:57 EST
(In reply to Stephen Gordon from comment #4)
> Xavier, how is group "foo" actually defined (and the policy set)? I thought
> the API for this didn't get accepted yet?

Until the blueprint linked from bug 978507 is completed (expected for Icehouse), the group's policy will be defined by the group filter the scheduler is using. In Havana both affinity and anti affinity filters are available, while in Grizzly only the anti affinity exists.
Comment 8 Ami Jeain 2014-01-27 06:02:55 EST
verified according to https://bugzilla.redhat.com/show_bug.cgi?id=1014948#c2:
I have now successfully created 2 instances in group, 2 in each one of the computes.
No errors found in nova (scheduler and compute)
Comment 10 errata-xmlrpc 2014-01-30 14:59:49 EST
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.


Note You need to log in before you can comment on or make changes to this bug.