From 1e00627b3bbb07f6d923461b6ac143a27e777f7e Mon Sep 17 00:00:00 2001 From: vivek Date: Fri, 13 Oct 2017 15:46:23 -0700 Subject: [PATCH] bgpd: Don't generate spurious warning on VNI deletion There are situations in which zebra may issue more than one delete notification, so BGP should not warn when it can't locate the VNI at delete. This is comparable to the situation when a withdraw is received but the route isn't present locally. Signed-off-by: Vivek Venkatraman Ticket: CM-17512 Reviewed By: Trivial Testing Done: Manual --- bgpd/bgp_evpn.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/bgpd/bgp_evpn.c b/bgpd/bgp_evpn.c index 49808e7cdd..e3158e2b10 100644 --- a/bgpd/bgp_evpn.c +++ b/bgpd/bgp_evpn.c @@ -4421,8 +4421,9 @@ int bgp_evpn_local_vni_del(struct bgp *bgp, vni_t vni) /* Locate VNI hash */ vpn = bgp_evpn_lookup_vni(bgp, vni); if (!vpn) { - zlog_warn("%u: VNI hash entry for VNI %u not found at DEL", - bgp->vrf_id, vni); + if (bgp_debug_zebra(NULL)) + zlog_warn("%u: VNI hash entry for VNI %u not " + "found at DEL", bgp->vrf_id, vni); return 0; } -- 2.39.5