absolute-limits sometimes returns negative value

Bug #1370867 reported by Akihiro Motoki on 2014-09-18
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
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
+----+------+--------+------------+-----------i-+----------+
| 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 |
| maxSecurityGroupRules | 20 |
| maxTotalKeypairs | 100 |
| totalRAMUsed | -2048 |
| maxSecurityGroups | 10 |*
| totalFloatingIpsUsed | 0 |
| totalInstancesUsed | -1 |
| totalSecurityGroupsUsed | 1 |
| maxTotalFloatingIps | 10 |
| maxTotalInstances | 10 |
| totalCoresUsed | -1 |
| maxTotalCores | 20 |
+-------------------------+-------+

Sean Dague (sdague) wrote :

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.

Changed in nova:
status: New → Incomplete
Akihiro Motoki (amotoki) wrote :

I am exploring how to reproduce it, but cannot so far. I experienced this three times in these two month in our lab using Icehouse with ~20 nodes. I noticed this because Horizon Overview page (the default login page) cannot be displayed with a traceback. I will keep exploring how to repro.
Note that the full tempest jobs are run daily and the database backend is Galera cluster.

(On Horizon side, it brings bad user experience as the default page after login is affected, so a workaround to replace negative values in total*Used with 0 is under review and it will be backported to Icehouse.)

Joe Gordon (jogo) wrote :

Can you include a link to the patch unde review

Akihiro Motoki (amotoki) wrote :

There is no patch to nova at the moment as I don't have a reproduce scenario so far.
Horizon side bug related to this issue is bug 1370869 (and it was shipped as a part of RC1).

Sean Dague (sdague) on 2015-04-01
tags: added: quotas
Changed in nova:
status: Incomplete → Confirmed
importance: Undecided → Medium
Alan Pevec (apevec) on 2015-11-24
tags: removed: icehouse-backport-potential

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY

Changed in nova:
importance: Medium → Undecided
status: Confirmed → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers