yahoo-eng-team team mailing list archive

[Rui Chen <chenrui.momo@xxxxxxxxx>]

Public bug reported:

Reproduce steps:

1. boot instanceA with anti-affinity policy server group, instanceA start on hostA.
2. resize instanceA, instanceA was migrated to hostB, wait for verify resize.
3. boot instanceB with the same server group, the instanceB was scheduled to hostA because of anti-affinity policy.
4. resize-revert instanceA, the instanceA restart on the source host(hostA).
5. the instanceA and instanceB run on same host (hostA), the anti-affinity policy is broken.

When we setup the server group in booting instance logic, the source and
destination hosts of resizing/migrating instance should been add into
server group hosts in order to impact on the schedule of other instance
with same server group.

** Affects: nova
     Importance: Undecided
     Assignee: Rui Chen (kiwik-chenrui)
         Status: New


** Tags: compute

** Changed in: nova
     Assignee: (unassigned) => Rui Chen (kiwik-chenrui)

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

Title:
  resize-revert broken anti-affinity policy of server group

Status in OpenStack Compute (Nova):
  New

Bug description:
  Reproduce steps:

  1. boot instanceA with anti-affinity policy server group, instanceA start on hostA.
  2. resize instanceA, instanceA was migrated to hostB, wait for verify resize.
  3. boot instanceB with the same server group, the instanceB was scheduled to hostA because of anti-affinity policy.
  4. resize-revert instanceA, the instanceA restart on the source host(hostA).
  5. the instanceA and instanceB run on same host (hostA), the anti-affinity policy is broken.

  When we setup the server group in booting instance logic, the source
  and destination hosts of resizing/migrating instance should been add
  into server group hosts in order to impact on the schedule of other
  instance with same server group.

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