-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bgpd: Ignore routes from evpn if VRF is unknown #16068
Conversation
@ton31337 -> opinions here on needing a new test case in topotests? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm curious how it pass this test is_route_matching_for_vrf()
in bgp_evpn_route_entry_install_if_vrf_match()
. Something weird to me.
@piotrsuchy are you able to reproduce this deterministically?
it seems like this would be a good time to add a topo test here |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code looks good, waiting on @ton31337 's question about reproducing this
Hello, sorry for the late response. Unfortunately I don't have a minimal deterministic reproduction - back when this issue appeared, we had a test suite on a pretty complex containerlab-like environment with our propriety software and configuration that was able to reproduce this issue, that came down to the reproduction steps mentioned in the linked issue above. The patch in this PR has made it so the issue wasn't reproducible and currently we have this patch running on production. Sadly I don't have a way to mimic this environment easily to reproduce this bug only. In the future when I have more cycles I might get back to this and try to have a minimal reproduction. |
Ok, I see I was most likely hooked on |
Sure! I added the additional log if this condition is hit. |
Fix for a bug, where FRR fails to install route received for an unknown but later-created VRF - detailed description can be found here FRRouting#13708 Signed-off-by: Piotr Suchy <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, just waiting on other comments/etc.
@Mergifyio backport dev/10.1 |
✅ Backports have been created
|
bgpd: Ignore routes from evpn if VRF is unknown (backport #16068)
Fix for a bug, where FRR fails to install route received for an unknown but later-created VRF - detailed description can be found here:
#13708
This is our internal bug fix we introduced that fixed this issue for us shortly after submitting the issue report.