yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: neutron
       Status: Fix Committed => Fix Released

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

Title:
  Updating subnet gateway_ip doesn't update router port and invalidates
  floating ips

Status in OpenStack Neutron (virtual network service):
  Fix Released

Bug description:
  In doing some testing with devstack, I tried update the gateway_ip on
  a subnet.  I found that my running instances successfully updated
  their routing tables.  However, I noticed that my router port still
  maintained the old IP address.  Since I had floating ips associated
  with the router, I could not remove the router interface and add a new
  one.

  This got me wondering about the usefulness of allowing updates to
  gateway_ip on a subnet.

  Updating the gateway_ip effectively invalidates all of the existing
  floating ips because the instances associated with them change their
  routing tables.  So, changing gateway_ip is not as simple as calling
  update subnet.  One has to do the following:

  - Disassociated all of the floating IPs for instances on the subnet.
  - Remove the router port
  - Update the subnet's gateway_ip
  - Add a new router port
  - Re-associate floating IPs.

  Steps 2 and 4 wouldn't be necessary in the event that there is more
  than one router attached to the subnet but the floatingip issue
  remains.

  What use cases need the ability to update gateway_ip?  Are they worth
  the difficulty involved?

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