yahoo-eng-team team mailing list archive

[Dan Smith <dms@xxxxxxxxxxxxx>]

Public bug reported:

The following sequence of events will result in a corrupted instance
allocation in placement:

1. Instance running on host A, placement has allocations for instance on host A
2. Host A goes down
3. Instance is evacuated to host B, host B creates duplicated allocations in placement for instance
4. Host A comes up, notices that instance is gone, deletes all allocations for instance on both hosts A and B
5. Instance now has no allocations for a period
6. Eventually, host B will re-create the allocations for the instance

The period between #4 and #6 will have the scheduler making bad
decisions because it thinks host B is less loaded than it is.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  Evacuation will corrupt instance allocations

Status in OpenStack Compute (nova):
  New

Bug description:
  The following sequence of events will result in a corrupted instance
  allocation in placement:

  1. Instance running on host A, placement has allocations for instance on host A
  2. Host A goes down
  3. Instance is evacuated to host B, host B creates duplicated allocations in placement for instance
  4. Host A comes up, notices that instance is gone, deletes all allocations for instance on both hosts A and B
  5. Instance now has no allocations for a period
  6. Eventually, host B will re-create the allocations for the instance

  The period between #4 and #6 will have the scheduler making bad
  decisions because it thinks host B is less loaded than it is.

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