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 <vivek@cumulusmetworks.com>

Ticket: CM-17512
Reviewed By: Trivial
Testing Done: Manual
This commit is contained in:
vivek 2017-10-13 15:46:23 -07:00 committed by Donald Sharp
parent 637315fc78
commit 1e00627b3b

View File

@ -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;
}