Conflict when deleting allocations for an instance that hasn't finished building
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Unassigned |
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-
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:
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: placement |
Changed in nova: | |
status: | In Progress → Confirmed |
assignee: | Matt Riedemann (mriedem) → nobody |
Changed in nova: | |
status: | Confirmed → Incomplete |
no longer affects: | nova/stein |
no longer affects: | nova/train |
Changed in nova: | |
status: | Incomplete → In Progress |
http:// logstash. openstack. org/#dashboard/ file/logstash. json?query= message% 3A%5C%22HTTP% 20exception% 20thrown% 3A%20Failed% 20to%20delete% 20allocations% 20for%20consume r%5C%22% 20AND%20message %3A%5C% 22Inventory% 20and%2For% 20allocations% 20changed% 20while% 20attempting% 20to%20allocate %3A%20Another% 20thread% 20concurrently% 20updated% 20the%20data. %5C%22% 20AND%20tags% 3A%5C%22screen- n-api.txt% 5C%22&from= 7d