Nova fails to correctly update the quota when deleting lots of VMs, some of which previously failed due to a quota error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
High
|
Pushkar Umaranikar |
Bug Description
When VMs goes to ERROR state after the block device mapping nova updates the quota for adding the instance/CPU/RAM to the quota
but when we delete those VMs nova forgets the release/update the CPU/RAM/Instance quota
Steps to reproduce:
1. Set the quota limit for volumes to 10 and VMs to 50
2. create 20 VMs by using option boot from volume from horizon
Observation:
10 VMs comes to active state and 10 goes to ERROR state (As expected)
3. delete all VMs
Expectation: CPU/RAM/Instance used quota will come to "0"
Actual: CPU/RAM/Instance quota is not coming to "0"
CPU used quota shows 10 (As the VM is created from M1.SMALL flavor)
Instance quota shows 10
RAM quota shows 20480MB
which is quite unexpected
Its seems it is a blocker for Ocata release
I am running from the stable/Ocata
Changed in nova: | |
status: | New → Confirmed |
summary: |
- Nova ignores to update the quota for VMs in error + Nova fails to correctly update the quota when deleting lots of VMs, some + of which previously failed due to a quota error |
Changed in nova: | |
assignee: | nobody → Sarafraj Singh (sarafraj-singh) |
Changed in nova: | |
assignee: | Sarafraj Singh (sarafraj-singh) → Pushkar Umaranikar (pushkar-umaranikar) |
Thats expected, you have to delete the instance to remove the quota usage.
That is by design, as its very possible for an instance that is in the ERROR state to be running and user hypervisor resources, IPs, volumes, etc.
You must delete to remove the quota usage.
I don't believe thats a recent change. Did you see different behaviour on a previous release?