← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1836754] Re: Conflict when deleting allocations for an instance that hasn't finished building

 

This goes back to Stein because https://review.opendev.org/#/c/591597/
changed the method from using DELETE /allocations/{consumer_id} to the
GET/PUT dance.

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

** Also affects: nova/train
   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/1836754

Title:
  Conflict when deleting allocations for an instance that hasn't
  finished building

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) stein series:
  New
Status in OpenStack Compute (nova) train series:
  New

Bug description:
  Description
  ===========

  When deleting an instance that hasn't finished building, we'll
  sometimes get a 409 from placement as such:

  Failed to delete allocations for consumer 6494d4d3-013e-478f-
  9ac1-37ca7a67b776. Error: {"errors": [{"status": 409, "title":
  "Conflict", "detail": "There was a conflict when trying to complete
  your request.\\\\n\\\\n Inventory and/or allocations changed while
  attempting to allocate: Another thread concurrently updated the data.
  Please retry your update  ", "code": "placement.concurrent_update",
  "request_id": "req-6dcd766b-f5d3-49fa-89f3-02e64079046a"}]}

  Steps to reproduce
  ==================

  1. Boot an instance
  2. Don't wait for it to become active
  3. Delete it immediately

  Expected result
  ===============

  The instance deletes successfully.

  Actual result
  =============

  Nova bubbles up that error from Placement.

  Logs & Configs
  ==============

  This is being hit at a low rate in various CI tests, logstash query is
  here:

  http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Inventory%20and%2For%20allocations%20changed%20while%20attempting%20to%20allocate%3A%20Another%20thread%20concurrently%20updated%20the%20data%5C%22%20AND%20filename%3A%5C
  %22job-output.txt%5C%22

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


References