bgpd: Do not withdraw EVPN route to update

Previously bgpd needed to send a withdraw followed by an install
to update an EVPN prefix route. With refcount tracking in zebra
this is no longer needed

Signed-off-by: Christopher Dziomba <christopher.dziomba@telekom.de>

diff --git a/bgpd/bgp_route.c b/bgpd/bgp_route.c
index 0c3f983f42bb2e95da7c48b95bdfb417e5d54ee2..4a6ad402dbd5b04a8fc49063e752ce111e10e4a2 100644 (file)
--- a/bgpd/bgp_route.c
+++ b/bgpd/bgp_route.c
@@ -3968,14 +3968,6 @@ static void bgp_process_main_one(struct bgp *bgp, struct bgp_dest *dest,
                        || new_select->sub_type == BGP_ROUTE_AGGREGATE
                        || new_select->sub_type == BGP_ROUTE_IMPORTED)) {
 
-                       /* if this is an evpn imported type-5 prefix,
-                        * we need to withdraw the route first to clear
-                        * the nh neigh and the RMAC entry.
-                        */
-                       if (old_select &&
-                           is_route_parent_evpn(old_select))
-                               bgp_zebra_withdraw_actual(dest, old_select, bgp);
-
                        bgp_zebra_route_install(dest, new_select, bgp, true,
                                                NULL, false);
                } else {