Build #2,783

FreeRangeRouting Protocol Suite

Build result summary


44 minutes
da579bf9ffc3ca0406d4d97f42446910a03f405e da579bf9ffc3ca0406d4d97f42446910a03f405e
Total tests
Failing since
#2764 (Changes by Mark Stapp <>)
Fixed in
#2825 (Changes by David Lamparter)
No failed tests found, a possible compilation error occurred.



This build has been failing since #2764
No one has taken responsibility

Code commits

Author Commit Message Commit date
Sri Mohana Singamsetty <> Sri Mohana Singamsetty <> da579bf9ffc3ca0406d4d97f42446910a03f405e da579bf9ffc3ca0406d4d97f42446910a03f405e Merge pull request #5432 from chiragshah6/evpn_dev2
bgpd: Handle possible non-selection of local route
Chirag Shah Chirag Shah 7ab604ab79d60b839e2d38020fd6ccbe0be033b8 m 7ab604ab79d60b839e2d38020fd6ccbe0be033b8 bgpd: Handle possible non-selection of local route
In rare situations, the local route in a VNI may not get selected as the
best route. One situation is during a race between bgp and zebra which
was addressed in a prior commit. This change addresses another situation
where due to a change of tunnel IP, it is possible that a received route
may be selected as the best route if the path selection needs to take
next hop IPs into consideration. This is a pretty convoluted scenario,
but the code should handle it and delete and withdraw the local route
as well as (re)install the received route.

Ticket: CM-24114
Reviewed By: CCR-9487
Testing Done:
1. Manual tests - note, problem is not readily reproducible
2. evpn-smoke - results documented in the ticket

Signed-off-by: Vivek Venkatraman <>
Signed-off-by: Chirag Shah <>