yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #81033
[Bug 1851609] Re: Add an option for graceful l3 agent shutdown
Reviewed: https://review.opendev.org/693323
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=566351761318aa1f33650ba4d78b55cc6a4f8f7b
Submitter: Zuul
Branch: master
commit 566351761318aa1f33650ba4d78b55cc6a4f8f7b
Author: Oleg Bondarev <obondarev@xxxxxxxxxxxx>
Date: Wed Nov 6 11:43:57 2019 +0400
Support L3 agent cleanup on shutdown
Add an option to delete all routers on agent shutdown.
Closes-Bug: #1851609
Change-Id: I7a4056680d8453b2ef2dcc853437a0ec4b3e8044
** 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/1851609
Title:
Add an option for graceful l3 agent shutdown
Status in neutron:
Fix Released
Bug description:
If KillMode in systemd config of a neutron l3 agent service is set to
'process' - it will not kill child processes on main service stop -
this is useful when we don't want data-plane downtime on agent
stop/restart due to keepalived exit.
However in some cases graceful cleanup on l3 agent shutdown is needed
- like with containerised control plane, when kubernetes kills
l3-agent pod, it automatically kills its children (keepalived
processes) in non-graceful way, so that keepalived does not clear
VIPs. This leads to a situation when same VIP is present on different
nodes and hence to long downtime.
The proposal is to add a new l3 agent config so that it handles stop
(SIGTERM) by deleting all routers. For HA routers it results in
graceful keepalived shutdown.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1851609/+subscriptions
References