absolute-limits sometimes returns negative value
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Nova icehouse 2014.1.2
There is a case where nova absolute-limits returns negative values for *Used fields
even when there is no instance for the project (as below)
*Used should be 0 when there is no instance.
Note that after it happened, I booted one instance.
Then *Used fields became the correct value (1 for totalInstancesUsed)
After that the instance was deleted and *Used fields was reset to 0.
ubuntu@dev03:~$ nova list
+----+-
| ID | Name | Status | Task State | Power State | Networks |
+----+-
+----+-
ubuntu@dev03:~$ nova absolute-limits
+------
| Name | Value |
+------
| maxServerMeta | 128 |
| maxPersonality | 5 |
| maxImageMeta | 128 |
| maxPersonalitySize | 10240 |
| maxTotalRAMSize | 51200 |
| maxSecurityGrou
| maxTotalKeypairs | 100 |
| totalRAMUsed | -2048 |
| maxSecurityGroups | 10 |*
| totalFloatingIp
| totalInstancesUsed | -1 |
| totalSecurityGr
| maxTotalFloatingIps | 10 |
| maxTotalInstances | 10 |
| totalCoresUsed | -1 |
| maxTotalCores | 20 |
+------
tags: | added: quotas |
Changed in nova: | |
status: | Incomplete → Confirmed |
importance: | Undecided → Medium |
tags: | removed: icehouse-backport-potential |
Can you create a reproduce scenario? We know there are some consistency issues in limits, but we really need a reproduce scenario to figure out what's up.