This bug is still relevant. Excerpt from https://review.openstack.org/#/c/579163/:
The current behavior status: 200 { "allocations": {} } is wrong because the response payload doesn't conform to the expected format, which would contain a consumer_generation, project_id, and user_id. That those fields don't make sense in a context where there's no consumer is another motivator for making this a 4xx failure. ** Changed in: nova Status: Won't Fix => Triaged -- 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): In Progress 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp