← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1512858] [NEW] Default gateway in fip namespace not updated after a subnet-update

 

Public bug reported:

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

** Affects: neutron
     Importance: Undecided
         Status: New

** Summary changed:

- Default route in fip namespace not updated after a subnet-update
+ Default gateway in fip namespace not updated after a subnet-update

** Description changed:

  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 
+ 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

-- 
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:
  New

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


Follow ups