yahoo-eng-team team mailing list archive

[Bogdan Dobrelya <1785568@xxxxxxxxxxxxxxxxxx>]

I believe this should be fixed in Nova Placement. Not sure this belongs
to tripleo.

** Also affects: nova
   Importance: Undecided
       Status: New

** Changed in: nova
       Status: New => Incomplete

** Changed in: tripleo
       Status: Triaged => Won't Fix

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

Title:
  Multiple migration requests for same vm might fail

Status in OpenStack Compute (nova):
  Incomplete
Status in tripleo:
  Won't Fix

Bug description:
  If there are multiple migration requests for the same instance, 
  the placement inventory might not be cleaned up in time, 
  leading to further migration requests to this compute to fail: 

  Allocation for VCPU on resource provider b6d1973f-
  bc39-4ea0-8d28-15f988f762e1 violates min_unit, max_unit, or step_size.
  Requested: 5, min_unit: 1, max_unit: 4, step_size: 1 Placement API
  returning an error response: Unable to allocate inventory: Unable to
  create allocation for 'VCPU' on resource provider The requested amount
  would violate inventory constraints

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