The records in quotausages table for floatingip are not updated immediately after delete some (or all) floatingips.
For example, if we set quota for floatingip to 5, create 5 floatingips and remove all of them, after that we can't create new floatingip:
The error "Quota exceeded for resources: ['floatingip']." occurs.
And at this time in mysql db we can see following:
mysql> select * from quotausages;
+----------------------------------+------------+-------+--------+----------+
| tenant_id | resource | dirty | in_use | reserved |
+----------------------------------+------------+-------+--------+----------+
| fae4b729e0d543199331d6be300074fc | floatingip | 0 | 5 | 0 |
| fae4b729e0d543199331d6be300074fc | network | 0 | 1 | 0 |
+----------------------------------+------------+-------+--------+----------+
Steps to reproduce:
1. $ neutron quota-update --floatingip 5
2. $ for i in $(seq 1 5); do neutron floatingip-create public; done
3. Try to create another one floatingip (should not be created):
$ neutron floatingip-create public
Quota exceeded for resources: ['floatingip'].
4. $ for ip in $(neutron floatingip-list -f csv -c id --quote=none | grep -v id); do neutron floatingip-delete $ip done
5. Try to create another one floatingip:
$ neutron floatingip-create public
Quota exceeded for resources: ['floatingip'].
6. Check quotas info in db:
mysql> use neutron
mysql> select * from quotausages;
Full log here: http://paste.openstack.org/show/483767/
It is even worse than that. I can see big differences in my setup between actually allocated floating IPs and the value in the quotausages table. See https:/
mysql> SELECT q.tenant_
+------
| tenant_id | in_use | floating_ips |
+------
| 08609b63401f436
| 3a1e97ffa74f429
| 7829521236b143d
| 8d04de0a40cc441
| d7400e965d5a40a
| f62d544271e6416
+------
6 rows in set (0.00 sec)