yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #16620
[Bug 1334278] [NEW] limits with tenant parameter returns wrong maxTotal* values
Public bug reported:
When querying for the "absolute limits" of a specific tenant
the maxTotal* values reported aren't correct.
How to reproduce:
for example using devstack...
OS_TENANT_NAME=demo (11b2b129994844798c98f437d9809a9c)
OS_USERNAME=demo
$nova absolute-limits
+-------------------------+-------+
| Name | Value |
+-------------------------+-------+
| maxServerMeta | 128 |
| maxPersonality | 5 |
| maxImageMeta | 128 |
| maxPersonalitySize | 10240 |
| maxTotalRAMSize | 1000 |
| maxSecurityGroupRules | 20 |
| maxTotalKeypairs | 100 |
| totalRAMUsed | 128 |
| maxSecurityGroups | 10 |
| totalFloatingIpsUsed | 0 |
| totalInstancesUsed | 2 |
| totalSecurityGroupsUsed | 1 |
| maxTotalFloatingIps | 10 |
| maxTotalInstances | 10 | <-----------------------
| totalCoresUsed | 2 |
| maxTotalCores | 10 | <-----------------------
+-------------------------+-------+
OS_TENANT_NAME=admin (b0f08277004b43aab516ae7dbf36ff51)
OS_USERNAME=admin
$nova absolute-limits
+-------------------------+--------+
| Name | Value |
+-------------------------+--------+
| maxServerMeta | 128 |
| maxPersonality | 5 |
| maxImageMeta | 128 |
| maxPersonalitySize | 10240 |
| maxTotalRAMSize | 151200 |
| maxSecurityGroupRules | 20 |
| maxTotalKeypairs | 100 |
| totalRAMUsed | 1152 |
| maxSecurityGroups | 10 |
| totalFloatingIpsUsed | 0 |
| totalInstancesUsed | 18 |
| totalSecurityGroupsUsed | 1 |
| maxTotalFloatingIps | 10 |
| maxTotalInstances | 30 |
| totalCoresUsed | 18 |
| maxTotalCores | 30 |
+-------------------------+--------+
$nova absolute-limits --tenant 11b2b129994844798c98f437d9809a9c
+-------------------------+--------+
| Name | Value |
+-------------------------+--------+
| maxServerMeta | 128 |
| maxPersonality | 5 |
| maxImageMeta | 128 |
| maxPersonalitySize | 10240 |
| maxTotalRAMSize | 151200 |
| maxSecurityGroupRules | 20 |
| maxTotalKeypairs | 100 |
| totalRAMUsed | 128 |
| maxSecurityGroups | 10 |
| totalFloatingIpsUsed | 0 |
| totalInstancesUsed | 2 |
| totalSecurityGroupsUsed | 1 |
| maxTotalFloatingIps | 10 |
| maxTotalInstances | 30 | <-------------------
| totalCoresUsed | 2 |
| maxTotalCores | 30 | <-------------------
+-------------------------+--------+
note: arrows show the wrong values.
Seems that maxTotal* shows the values for the current tenant and not what is specified by "--tenant"
as expected.
tested in havana and icehouse-1
** Affects: nova
Importance: Undecided
Status: New
--
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/1334278
Title:
limits with tenant parameter returns wrong maxTotal* values
Status in OpenStack Compute (Nova):
New
Bug description:
When querying for the "absolute limits" of a specific tenant
the maxTotal* values reported aren't correct.
How to reproduce:
for example using devstack...
OS_TENANT_NAME=demo (11b2b129994844798c98f437d9809a9c)
OS_USERNAME=demo
$nova absolute-limits
+-------------------------+-------+
| Name | Value |
+-------------------------+-------+
| maxServerMeta | 128 |
| maxPersonality | 5 |
| maxImageMeta | 128 |
| maxPersonalitySize | 10240 |
| maxTotalRAMSize | 1000 |
| maxSecurityGroupRules | 20 |
| maxTotalKeypairs | 100 |
| totalRAMUsed | 128 |
| maxSecurityGroups | 10 |
| totalFloatingIpsUsed | 0 |
| totalInstancesUsed | 2 |
| totalSecurityGroupsUsed | 1 |
| maxTotalFloatingIps | 10 |
| maxTotalInstances | 10 | <-----------------------
| totalCoresUsed | 2 |
| maxTotalCores | 10 | <-----------------------
+-------------------------+-------+
OS_TENANT_NAME=admin (b0f08277004b43aab516ae7dbf36ff51)
OS_USERNAME=admin
$nova absolute-limits
+-------------------------+--------+
| Name | Value |
+-------------------------+--------+
| maxServerMeta | 128 |
| maxPersonality | 5 |
| maxImageMeta | 128 |
| maxPersonalitySize | 10240 |
| maxTotalRAMSize | 151200 |
| maxSecurityGroupRules | 20 |
| maxTotalKeypairs | 100 |
| totalRAMUsed | 1152 |
| maxSecurityGroups | 10 |
| totalFloatingIpsUsed | 0 |
| totalInstancesUsed | 18 |
| totalSecurityGroupsUsed | 1 |
| maxTotalFloatingIps | 10 |
| maxTotalInstances | 30 |
| totalCoresUsed | 18 |
| maxTotalCores | 30 |
+-------------------------+--------+
$nova absolute-limits --tenant 11b2b129994844798c98f437d9809a9c
+-------------------------+--------+
| Name | Value |
+-------------------------+--------+
| maxServerMeta | 128 |
| maxPersonality | 5 |
| maxImageMeta | 128 |
| maxPersonalitySize | 10240 |
| maxTotalRAMSize | 151200 |
| maxSecurityGroupRules | 20 |
| maxTotalKeypairs | 100 |
| totalRAMUsed | 128 |
| maxSecurityGroups | 10 |
| totalFloatingIpsUsed | 0 |
| totalInstancesUsed | 2 |
| totalSecurityGroupsUsed | 1 |
| maxTotalFloatingIps | 10 |
| maxTotalInstances | 30 | <-------------------
| totalCoresUsed | 2 |
| maxTotalCores | 30 | <-------------------
+-------------------------+--------+
note: arrows show the wrong values.
Seems that maxTotal* shows the values for the current tenant and not what is specified by "--tenant"
as expected.
tested in havana and icehouse-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1334278/+subscriptions
Follow ups
References