yahoo-eng-team team mailing list archive

[David Kranz <dkranz@xxxxxxxxxx>]

Public bug reported:

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' ecen 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. But this problem shows in the
nightly run without tenant isolation:

http://logs.openstack.org/periodic-qa/periodic-tempest-dsvm-full-non-
isolated-master/2bc5ead/console.html

** 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/1347156

Title:
  deleting floating-ip in nova-network does not free quota

Status in OpenStack Compute (Nova):
  New

Bug description:
  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' ecen 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. But this problem
  shows in the nightly run without tenant isolation:

  http://logs.openstack.org/periodic-qa/periodic-tempest-dsvm-full-non-
  isolated-master/2bc5ead/console.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1347156/+subscriptions