← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1313720] [NEW] ipallocations not cleaned after floating ip delete

 

Public bug reported:

I have a limited floatingip pool for revolving set of users.
I have a script that will run a neutron floatingip-delete on IPs that are not associated with an instance and a neutron router-gateway-clear on routers that don't have any floatingips associated with them.

I was still getting the message "Error: Failed to set gateway No more IP
addresses available on network " when new users were trying to set the
gateway on their router.

My current workaround is to run a database query that selects the ips
from my floatingip pool that do not have an associated port and delete
the record.

delete from ipallocations where ip_address in (
    select * from (
        select ip_address from ipallocations left join ports on ipallocations.port_id = ports.id
        where ports.id is NULL and ip_address like '{3-octets-of-fip-pool}%'
) as p);

This restores capability to set gateways and allocate floating ips.

I'm running the RDO build of 2014.1

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1313720

Title:
  ipallocations not cleaned after floating ip delete

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  I have a limited floatingip pool for revolving set of users.
  I have a script that will run a neutron floatingip-delete on IPs that are not associated with an instance and a neutron router-gateway-clear on routers that don't have any floatingips associated with them.

  I was still getting the message "Error: Failed to set gateway No more
  IP addresses available on network " when new users were trying to set
  the gateway on their router.

  My current workaround is to run a database query that selects the ips
  from my floatingip pool that do not have an associated port and delete
  the record.

  delete from ipallocations where ip_address in (
      select * from (
          select ip_address from ipallocations left join ports on ipallocations.port_id = ports.id
          where ports.id is NULL and ip_address like '{3-octets-of-fip-pool}%'
  ) as p);

  This restores capability to set gateways and allocate floating ips.

  I'm running the RDO build of 2014.1

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


Follow ups

References