yahoo-eng-team team mailing list archive

[Chris Dent <cdent+lp@xxxxxxxxxxxxx>]

Public bug reported:

If we write some allocations with PUT /allocations/{uuid} at modern
microversions, a consumer record is created for {uuid} and a generation
is created for that consumer. Each subsequent attempt to PUT
/allocations/{uuid} must include a matching consumer generation.

If the allocations for a consumer are cleared (either DELETE, or PUT
/allocations/{uuid} with an empty dict of allocations) two things go
awry:

* the consumer record, with a generation, stays around
* GET /allocations/{uuid} returns the following:

   {u'allocations': {}}

That is, no generation is provided, and we have no way figure one out
other than inspecting the details of the error response.

Some options to address this:

* Return the generation in that response
* When the allocations for a consumer go empty, remove the consumer
* Something else?

** 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/1778591

Title:
  GET /allocations/{uuid} on a consumer with no allocations provides no
  generation

Status in OpenStack Compute (nova):
  Triaged

Bug description:
  If we write some allocations with PUT /allocations/{uuid} at modern
  microversions, a consumer record is created for {uuid} and a
  generation is created for that consumer. Each subsequent attempt to
  PUT /allocations/{uuid} must include a matching consumer generation.

  If the allocations for a consumer are cleared (either DELETE, or PUT
  /allocations/{uuid} with an empty dict of allocations) two things go
  awry:

  * the consumer record, with a generation, stays around
  * GET /allocations/{uuid} returns the following:

     {u'allocations': {}}

  That is, no generation is provided, and we have no way figure one out
  other than inspecting the details of the error response.

  Some options to address this:

  * Return the generation in that response
  * When the allocations for a consumer go empty, remove the consumer
  * Something else?

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