-
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
ospf6d: ospf6_route_add - stack repeats #6083
Conversation
Signed-off-by: Donald Slice <dslice@cumulusnetworks.com> Signed-off-by: Daniel Walton <dwalton@cumulusnetworks.com> Reviewed-by: Donald Sharp <sharpd@cumulusnetworks.com> Reviewed-by: Chirag Shah <chirag@cumulusnetworks.com> Ticket: CM-17238 This is a temporary fix until the root cause for CM-17238 has been resolved. The fix for CM-17238 will back this commit out.
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, will check back in a bit for checks to complete
Continuous Integration Result: SUCCESSFULCongratulations, this patch passed basic tests Tested-by: NetDEF / OpenSourceRouting.org CI System CI System Testrun URL: https://ci1.netdef.org/browse/FRR-FRRPULLREQ-11404/ This is a comment from an automated CI system. Warnings Generated during build:Debian 10 amd64 build: Successful with additional warningsDebian Package lintian failed for Debian 10 amd64 build:
|
💚 Basic BGPD CI results: SUCCESS, 0 tests failedResults table
For details, please contact louberger |
Note that this problem relates the issue reported by #852. The temporary fix proposed in the PR was what was used in Cumulus for the last couple of years. I also notice that in ArchLinux, they commented out the call to table->hook_add, which also made the crash stop. I'll start testing with that approach as well to see the ramification of that way of solving it. If anyone has any thoughts on this, feel free to offer them. |
To recreate this problem, bring up the following topology:
R1-R2 link is in area 0.0.0.0 Add "redistribute connected" or "redistribute static" on both R1 and R2. |
Decided to scrap this PR and resubmit with another approach that I believe actually addresses the issue. Running automated tests against it now and will submit a new PR soon. |
Signed-off-by: Donald Slice dslice@cumulusnetworks.com
Signed-off-by: Daniel Walton dwalton@cumulusnetworks.com
Reviewed-by: Donald Sharp sharpd@cumulusnetworks.com
Reviewed-by: Chirag Shah chirag@cumulusnetworks.com
Ticket: CM-17238
This is a temporary fix until the root cause for CM-17238 has been
resolved. The fix for CM-17238 will back this commit out.