Build #3,523

FreeRangeRouting Protocol Suite

Build: #3523 failed Changes by Mark Stapp <mjs@voltanet.io>

Build result summary

Details

Completed
Duration
516 minutes
Labels
version=frr-7_4-dev-2046-g832d7382cgit=https_//github_com/frrouting/frr_gitbuildurl=https_//ci1_netdef_org/browse/frr-frr-3523branch=master
Revision
832d7382c8829625106cd8140e9469a70510e55c 832d7382c8829625106cd8140e9469a70510e55c
Total tests
9767
Failing since
#3518 (Changes by David Lamparter)
Fixed in
#3537 (Changes by Russ White <russ@riw.us>)

Tests

Responsible

Code commits

Author Commit Message Commit date
Mark Stapp <mjs@voltanet.io> Mark Stapp <mjs@voltanet.io> 832d7382c8829625106cd8140e9469a70510e55c 832d7382c8829625106cd8140e9469a70510e55c Merge pull request #6780 from chiragshah6/evpn_dev2
zebra: vrf disable clean up evpn rmac and nxthp cache
Chirag Shah Chirag Shah 92475ca4873fd6ccf1f804e675c912c698c486ce m 92475ca4873fd6ccf1f804e675c912c698c486ce zebra: vrf disable clean up evpn rmac nxthp cache
In networking restart event, l3vni (vxlan) interface followed by
associated vrf interfaces go down/deleted.
L3vni (oper) down event (from zebra to bgp) triggers to
clean up/un-import evpn routes (one-by-one) from the vrf table,
zebra internally removes the route entry from nexthop and RMAC hash.
When all the routes references in nexthop and RMAC db removed,
both (nexthop/rmac) are suppose to be uninstalled from the
bridge fdb and neigh table.
While evpn routes removal in progress, a vrf disable event removes
l3vni to its vrf association.
Subsequent bgp to evpn routes removal does not clean up thus evpn routes
reference to nexthop and RMAC remains in zebra hash.
bridge fdb and neigh tables are flushed out since networking restart brings down
all interfaces which results in flush of fdb and neigh tables.
By product is the zebra does not install nexthop and rmac when routes are re-imported
into vrf in VNI/VRF up event.

The fix is in vrf disable event to flush all l3vni's nexthop and rmac db.

Ticket:CM-30338
Reviewed By:CCR-10489
Testing Done:

Performed multiple networking restart and checked neigh and
bridge fdb tables for respective nexthop and router mac entry
programmed.

Signed-off-by: Chirag Shah <chirag@cumulusnetworks.com>

Tests

Existing test failures 2
Status Test Failing since View job Duration
AssertionError: 2 tests failed
E   AssertionError: 2 tests failed
AssertionError: 2 tests failed
E   AssertionError: 2 tests failed

Jira issues

IssueDescriptionStatus
Unknown Issue TypeCCR-10489Could not obtain issue details from Jira
Unknown Issue TypeCM-30338Could not obtain issue details from Jira
Unknown Issue TypeFRR-7Could not obtain issue details from Jira