Public bug reported: 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 | +-------------------------+-------+ ** Affects: nova Importance: Undecided Status: New ** Tags: icehouse-backport-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1370867 Title: absolute-limits sometimes returns negative value Status in OpenStack Compute (Nova): New 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 | +-------------------------+-------+ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1370867/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp