Volume remains in attaching/reserved status, if the instance is deleted after TooManyInstances exception in nova-conductor
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Matt Riedemann | ||
Pike |
Fix Committed
|
Medium
|
Matt Riedemann | ||
Queens |
Fix Committed
|
Medium
|
Matt Riedemann | ||
Rocky |
Fix Released
|
Medium
|
s10 |
Bug Description
If a number of instances are booted from volumes in parallel and some of the build requests failed in nova-conductor with exception TooManyInstances [1] because of the setting quota.recheck_
If we delete this instances, their volumes will remain in attaching(
This bug is related to https:/
Steps to reproduce:
0. Set quota.recheck_
1. Set VCPU quota limits for the project to 1.
2. Create two instances with 1 VCPU in parallel.
3. One of this instances will be created and one will end up in the ERROR state. Or both of them will be in ERROR state.
4. Delete instances.
5. Volumes from errored instances will not be available, they can't be attached, they can't be deleted without permision in volume:force_delete cinder policy.
This bug exists at least in Pike (7ff1b28) and Queens (c5fe051).
---
[1] https:/
summary: |
- Volume remains in attaching/reserved status after TooManyInstances - exception in nova-conductor + Volume remains in attaching/reserved status, if the instance is deleted + after TooManyInstances exception in nova-conductor |
tags: | added: cells volumes |
Changed in nova: | |
assignee: | nobody → Matt Riedemann (mriedem) |
This is closer to this change https:/ /review. openstack. org/#/c/ 544748/