yahoo-eng-team team mailing list archive

[Pawel Koniszewski <pawel.koniszewski@xxxxxxxxx>]

Public bug reported:

Let's say we have a setup with 3 compute nodes (CN1, CN2 and CN3) and 3
controllers (in HA mode). There are 2 VMs with anti-affinity policy (the
same server group) running in the environment:

* CN1 - VM A (anti-affinity)
* CN2 - VM B (anti-affinity)
* CN3 - empty

If we trigger live migration of VM A and then trigger live migration of
VM B without waiting for scheduling phase of VM A to complete we will
end up with anti-affinity policy violated:

* CN1 - empty
* CN2 - empty
* CN3 - VM A, VM B (both with anti-affinity policy)

Workaround is to wait few seconds and let scheduler finish the job for
the first VM.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: anti-affinity live-migration scheduler

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

Title:
  Simultaneous live migrations break anti-affinity policy

Status in OpenStack Compute (nova):
  New

Bug description:
  Let's say we have a setup with 3 compute nodes (CN1, CN2 and CN3) and
  3 controllers (in HA mode). There are 2 VMs with anti-affinity policy
  (the same server group) running in the environment:

  * CN1 - VM A (anti-affinity)
  * CN2 - VM B (anti-affinity)
  * CN3 - empty

  If we trigger live migration of VM A and then trigger live migration
  of VM B without waiting for scheduling phase of VM A to complete we
  will end up with anti-affinity policy violated:

  * CN1 - empty
  * CN2 - empty
  * CN3 - VM A, VM B (both with anti-affinity policy)

  Workaround is to wait few seconds and let scheduler finish the job for
  the first VM.

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