It seems that when you allocate a floating-ip in a tenant with nova-network,
its quota is never returned after calling 'nova floating-ip-delete'
even though 'nova floating-ip-list' shows it gone.
This behavior applies to each tenant individually. The gate tests are passing
because they all run with tenant isolation.
The root cause of the problem is cooperation between
commit 23a27e47 and cbbb9de5. db layer code return floatingip_ref
but object layer didn't. This patch fixed the problem by adding return
value from object layer.
Reviewed: https:/ /review. openstack. org/109220 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=77a7d145426 00f2badcdf048fe 6b586a0ff27e30
Committed: https:/
Submitter: Jenkins
Branch: master
commit 77a7d14542600f2 badcdf048fe6b58 6a0ff27e30
Author: jichenjc <email address hidden>
Date: Sat Jul 19 18:47:19 2014 +0800
Commit quota when deallocate floating ip
It seems that when you allocate a floating-ip in a tenant with nova-network,
its quota is never returned after calling 'nova floating-ip-delete'
even though 'nova floating-ip-list' shows it gone.
This behavior applies to each tenant individually. The gate tests are passing
because they all run with tenant isolation.
The root cause of the problem is cooperation between
commit 23a27e47 and cbbb9de5. db layer code return floatingip_ref
but object layer didn't. This patch fixed the problem by adding return
value from object layer.
Change-Id: Ide1a338b6c3367 6311028e8738150 e146324a8ee
Closes-Bug: #1347156