diff options
| author | Donald Sharp <sharpd@nvidia.com> | 2024-10-14 11:25:32 -0400 |
|---|---|---|
| committer | Mergify <37929162+mergify[bot]@users.noreply.github.com> | 2024-10-15 19:05:50 +0000 |
| commit | cf9c02a8b1592be6abc68345e1d1a364b44354f9 (patch) | |
| tree | 66d51385cb295d3e75a10678cea1af12ea753705 /tests/topotests/bgp_oad/test_bgp_oad.py | |
| parent | dc1a3111bfe4129cc27b132dfeda64ccddffa4bb (diff) | |
zebra: Prevent a kernel route from being there when a connected should
There exists a series of events where a kernel route is learned
first( that happens to be exactly what a connected route should be )
and FRR ends up with both a kernel route and a connected route,
leaving us in a very strange spot. This code change just mirrors
the existing code of if there is a connected route drop the kernel
route. Here we just do the reverse, if we have a kernel route
already and a connected should be created, remove the kernel and
keep the connected.
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
(cherry picked from commit 74e25198e74c4066b630515d2971c3c9381d70f2)
Diffstat (limited to 'tests/topotests/bgp_oad/test_bgp_oad.py')
0 files changed, 0 insertions, 0 deletions