[202405] Add log ignore to account for FDB flush race condition #15798
+1
−7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
During fdb/test_fdb_mac_learning.py::testARPCompleted, syslog will output the following error log: ``` ERR swss#orchagent: :- update: Failed to get port by bridge port ID 0x3a00000000155c. ``` This is not an actual error, but a minor race condition - it is caused by Broadcom SAI sending a FDB AGED event after the FDB entry has been flushed, causing orchagent to check on a bridge port that does not exist. Same issue as the one reoslved in sonic-net#9818
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of PR
Summary:
Fixes # (issue)
202405 version of #15797
During fdb/test_fdb_mac_learning.py::testARPCompleted, syslog will output the following error log:
This is not an actual error, but a minor race condition - it is caused by Broadcom SAI sending a FDB AGED event after the FDB entry has been flushed, causing orchagent to check on a bridge port that does not exist. Fix by extending log ignore to the test.
Same issue as the one reoslved in
#9818
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Test no longer fails with log analyzer on Broadcom platforms.
Any platform specific information?
Broadcom platforms only.
Supported testbed topology if it's a new test case?
Documentation