yahoo-eng-team team mailing list archive

[Chris Dent <cdent+lp@xxxxxxxxxxxxx>]

Public bug reported:

This is using microversion 1.28 of the placement API. I will start the
process of finding when this went wrong after submitting this bug. I'm
guessing at the start of POST to /allocations, but we'll see.

When a POST to /allocations contains multiple consumers each writing
some of their allocations to the same consumer, it is possible to "beat"
the inventory constraints.

In the gabbi test at http://paste.openstack.org/show/724317/ a resource
provider is created with an inventory of 2 VCPU. A POST is then made to
/allocations with three different consumers, each asking for 1 VCPU.
This works, and it should not because we then end up with a usage of 3
VCPU.


I found this while trying to chase some issues with consumer generations and allocations and fell into this hole.

** Affects: nova
     Importance: Medium
         Status: Triaged


** Tags: placement

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

Title:
  When POSTing to /allocations with multiple consumers it is possible
  violate inventory capacity constraints

Status in OpenStack Compute (nova):
  Triaged

Bug description:
  This is using microversion 1.28 of the placement API. I will start the
  process of finding when this went wrong after submitting this bug. I'm
  guessing at the start of POST to /allocations, but we'll see.

  When a POST to /allocations contains multiple consumers each writing
  some of their allocations to the same consumer, it is possible to
  "beat" the inventory constraints.

  In the gabbi test at http://paste.openstack.org/show/724317/ a
  resource provider is created with an inventory of 2 VCPU. A POST is
  then made to /allocations with three different consumers, each asking
  for 1 VCPU. This works, and it should not because we then end up with
  a usage of 3 VCPU.

  
  I found this while trying to chase some issues with consumer generations and allocations and fell into this hole.

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