-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[PATCH]: Update FRR patch 0009 to avoid inappropriate error messages #12912
Conversation
Signed-off-by: Stephen Xu <[email protected]>
|
/easycla |
@theasianpianist can you please review this PR? It's same as #12754 that you reviewed and approved earlier, but the PR got closed and re-created here to get away with the CLA issue. Thanks |
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.
thanks!
…onic-net#12912) Why I did it As described in detail in sonic-net#12753, the current FRR patch 0009-ignore-route-from-default-table.patch is causing unwanted FRR/zebra error logs. This change gets rid of the error messages for routes from kernel default table while these routes are ignored in prefix encoding. How I did it This fix updates the original 0009 patch by checking if the routes are from table default before printing the error logs. The original patch checks the same condition and ignores the routes from table default in prefix encoding. How to verify it Follow the steps to repro as described in sonic-net#12753. Also verify the test case ipfwd/test_nhop_count.py no longer fails due to the error messages. Signed-off-by: Stephen Xu <[email protected]>
Cherry-pick PR to 202205: #13004 |
This commit could not be cleanly cherry-picked to 202012. Please submit another PR. |
…onic-net#12912) Why I did it As described in detail in sonic-net#12753, the current FRR patch 0009-ignore-route-from-default-table.patch is causing unwanted FRR/zebra error logs. This change gets rid of the error messages for routes from kernel default table while these routes are ignored in prefix encoding. How I did it This fix updates the original 0009 patch by checking if the routes are from table default before printing the error logs. The original patch checks the same condition and ignores the routes from table default in prefix encoding. How to verify it Follow the steps to repro as described in sonic-net#12753. Also verify the test case ipfwd/test_nhop_count.py no longer fails due to the error messages. Signed-off-by: Stephen Xu <[email protected]>
…12912) (#13423) …(#12912) Why I did it As described in detail in #12753, the current FRR patch 0009-ignore-route-from-default-table.patch is causing unwanted FRR/zebra error logs. This change gets rid of the error messages for routes from kernel default table while these routes are ignored in prefix encoding. How I did it This fix updates the original 0009 patch by checking if the routes are from table default before printing the error logs. The original patch checks the same condition and ignores the routes from table default in prefix encoding. How to verify it Follow the steps to repro as described in #12753. Also verify the test case ipfwd/test_nhop_count.py no longer fails due to the error messages. #### Why I did it Resolve cherry-pick conflict for #12912
202012 branch PR merged: #13423 |
Fix issue #12753.
Why I did it
As described in detail in #12753, the current FRR patch
0009-ignore-route-from-default-table.patch
is causing unwanted FRR/zebra error logs. This change gets rid of the error messages for routes from kernel default table while these routes are ignored in prefix encoding.How I did it
This fix updates the original 0009 patch by checking if the routes are from table default before printing the error logs. The original patch checks the same condition and ignores the routes from table default in prefix encoding.
How to verify it
Follow the steps to repro as described in #12753.
Also verify the test case
ipfwd/test_nhop_count.py
no longer fails due to the error messages.Which release branch to backport (provide reason below if selected)