yahoo-eng-team team mailing list archive

[OpenStack Infra <1512858@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/241357
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a0f7153f9512ce313f0c8762889fe3ef6b455a32
Submitter: Jenkins
Branch:    master

commit a0f7153f9512ce313f0c8762889fe3ef6b455a32
Author: Rawlin Peters <rawlin.peters@xxxxxxx>
Date:   Tue Nov 3 13:09:27 2015 -0700

    Update default gateway in the fip namespace after subnet-update
    
    The gateway does not get updated after a subnet-update --gateway
    because the router is already subscribed to the fip namespace.
    On a restart, the fip namespace has no subscribers, which causes
    the gateway to be created. You shouldn't have to restart the L3
    agent in order to update the gateway.
    
    In order for the default gateway in the fip namespace to be updated
    after a subnet-update, the underlying code which sets the default
    gateway needs to be called even if the router is already subscribed to
    the fip namespace.
    
    The bit of code which is responsible for updating the default route has
    been refactored into its own method, update_gateway_port, which is then
    called after a 'subnet-update --gateway ...'. If the gateway has
    actually changed, the default route in the fip namespace will be
    updated.
    
    Change-Id: I0552c4a50ae09a6606e88395f7545179d02733dd
    Closes-Bug: #1512858


** Changed in: neutron
       Status: In Progress => 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/1512858

Title:
  Default gateway in fip namespace not updated after a subnet-update

Status in neutron:
  Fix Released

Bug description:
  After running the following command:

  neutron subnet-update --gateway <new gateway IP> <ext-net subnet ID>

  the default gateway does not get set to <new gateway IP> in the
  corresponding fip namespace until the l3-agent is restarted.

  The default gateway in the corresponding fip namespace should be
  updated right after running the "neutron subnet-update" command, just
  like it gets updated in the corresponding snat namespace.

  Current output:

  stack@stack:~$ sudo ip netns exec snat-7f799d98-66f5-47e9-a2d1-6fd21d41f181 ip r | grep default
  default via 10.127.10.223 dev qg-aa91f11a-97
  stack@stack:~$ sudo ip netns exec fip-25f35519-87ee-4c73-86dc-e0441a75734f ip r | grep default
  default via 10.127.10.223 dev fg-d9c0442f-5b

  stack@stack:~$ neutron subnet-update --gateway 10.127.10.222 09e385df-3bbf-474d-a0c1-bec63ad2069f
  Updated subnet: 09e385df-3bbf-474d-a0c1-bec63ad2069f

  stack@stack:~$ sudo ip netns exec snat-7f799d98-66f5-47e9-a2d1-6fd21d41f181 ip r | grep default
  default via 10.127.10.222 dev qg-aa91f11a-97
  stack@stack:~$ sudo ip netns exec fip-25f35519-87ee-4c73-86dc-e0441a75734f ip r | grep default
  default via 10.127.10.223 dev fg-d9c0442f-5b

  *restart the l3 agent*

  stack@stack:~$ sudo ip netns exec fip-25f35519-87ee-4c73-86dc-e0441a75734f ip r | grep default
  default via 10.127.10.222 dev fg-d9c0442f-5b

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