yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #05880
[Bug 1241317] Re: the quota usage of fixed_ips was not updated when booting a server using VLAN manager
*** This bug is a duplicate of bug 1204714 ***
https://bugs.launchpad.net/bugs/1204714
** This bug has been marked a duplicate of bug 1204714
VlanManager unnecessarly creates fixed_ip quota reservations
--
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/1241317
Title:
the quota usage of fixed_ips was not updated when booting a server
using VLAN manager
Status in OpenStack Compute (Nova):
New
Bug description:
Issue Description:
use nova.network.manager.VlanManager as network manager (specify in nova.conf)
1. when you use nova boot to launch an instance, it would not update the usage of fixed_ips
2. When use nova delete to delete instance, the usage of fixed_ips would be updated, and sometimes it would get the value "-1"
[root@sco22l3 ˜]# nova-manage project quota 6ac21d4dcabe45839e130e3e8f37b21c
Quota Limit In Use Reserved
metadata_items 128 0 0
injected_file_content_bytes 10240 0 0
volumes 10 0 0
gigabytes 1000 0 0
ram 51200 4096 2048
floating_ips 10 0 0
security_group_rules 20 0 0
instances 10 2 1
key_pairs 100 0 0
injected_files 5 0 0
cores 20 2 1
fixed_ips 10 0 0
injected_file_path_bytes 255 0 0
security_groups 50 0 0
[root@sco22l3 ˜]# nova list
+--------------------------------------+-------+--------+------------------------+
| ID | Name | Status | Networks |
+--------------------------------------+-------+--------+------------------------+
| 87725651-faa0-49f7-9d6e-7900e90fe148 | hwp-1 | ACTIVE | customernet=10.16.51.3 |
| 45dcedbe-61f1-43dd-902a-98f5b6e6948d | hwp-2 | ACTIVE | customernet=10.16.51.5 |
+--------------------------------------+-------+--------+------------------------+
[root@sco22l3 ˜]# nova delete 45dcedbe-61f1-43dd-902a-98f5b6e6948d
[root@sco22l3 ˜]# nova list
+--------------------------------------+-------+--------+------------------------+
| ID | Name | Status | Networks |
+--------------------------------------+-------+--------+------------------------+
| 87725651-faa0-49f7-9d6e-7900e90fe148 | hwp-1 | ACTIVE | customernet=10.16.51.3 |
+--------------------------------------+-------+--------+------------------------+
[root@sco22l3 ˜]# nova-manage project quota 6ac21d4dcabe45839e130e3e8f37b21c
Quota Limit In Use Reserved
metadata_items 128 0 0
injected_file_content_bytes 10240 0 0
volumes 10 0 0
gigabytes 1000 0 0
ram 51200 2048 2048
floating_ips 10 0 0
security_group_rules 20 0 0
instances 10 1 1
key_pairs 100 0 0
injected_files 5 0 0
cores 20 1 1
fixed_ips 10 -1 0
injected_file_path_bytes 255 0 0
security_groups 50 0 0
[root@sco22l3 ˜]#
The booting server does not update quota fixed-ip usage but deleting
server does update quota fixed-ip usage. This behavior not consistent
between booting and deleting should be a bug.
Above test is done on folsom. Via looking through codes, it is
probable it is able to happen on grizzely and havana.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1241317/+subscriptions
