yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

This was fixed in Pike with change:
https://review.openstack.org/#/c/469037/6/nova/scheduler/utils.py

If we needed to backport something to Ocata, it would have to be an
Ocata-only tactical fix.

** Changed in: nova
       Status: Confirmed => Fix Released

-- 
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/1600251

Title:
  live migration does not honor server group policy

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  What happens is that the live migration task uses the resource
  specification created when the instances was created and passes this
  to the scheduler to find a new host, marking its current host as
  excluded. This resource spec object includes the instance's group
  object which contains a list of instances in the group. The problem is
  that the instance group object in the resource spec reflects the list
  of instances in the group at the time the instance was created. Thus
  if you migrate the first instance to be assigned an anti affinity
  group it will think that the group has no other member instances and
  thus no compute nodes will be excluded. Only the most recently created
  instance assigned the anti affinity group will correctly exclude all
  nodes containing members of its group!

  There is code to update the instance group object in the resource spec
  but the resource spec object is only updated with this information if
  it is created by the live migration task, i.e. in the case of an
  instance without a resource spec in the request_specs database table.
  This will only be the case for instances created prior to the
  implementation of the requests_specs table.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1600251/+subscriptions