Public bug reported:
After running the following command:
neutron subnet-update --no-gateway <ext-net subnet ID>
the default gateway does not get cleaned in the corresponding snat and
fip namespace.
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 opposite operation, update a specified gateway from
no gateway by "neutron subnet-update --gateway <new gateway ip>".
** Affects: neutron
Importance: Undecided
Assignee: ZongKai LI (lzklibj)
Status: New
** Changed in: neutron
Assignee: (unassigned) => ZongKai LI (lzklibj)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1551596
Title:
Default route not get cleaned after external subnet updated with --no-
gateway in DVR scenario
Status in neutron:
New
Bug description:
After running the following command:
neutron subnet-update --no-gateway <ext-net subnet ID>
the default gateway does not get cleaned in the corresponding snat and
fip namespace.
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 opposite operation, update a specified
gateway from no gateway by "neutron subnet-update --gateway <new
gateway ip>".
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1551596/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
