Ignore log messages that should be warnings instead of error messages(Cisco) #16439
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
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
In Cisco platforms these error messages should be warning instead of error messages. We will be making the change but in the meanwhile, I am adding an ignore in log analyzer ignore files to avoid causing testcase failures
2025 Jan 9 12:56:34.229072 sfd-lt2-lc1 ERR syncd0#syncd: 09-01-2025 12:56:34.228 -E-API-0- src/hld/system/la_device_impl.cpp::10344 clear_snoop_configuration API returned: status = Leaba_Err: Entry requested not found: virtual la_status silicon_one::gibraltar::la_device_impl::do_clear_snoop_configuration(silicon_one::la_event_e):src/hld/system/la_device_impl.cpp:10361,
2025 Jan 9 12:57:23.457616 sfd-lt2-lc1 ERR syncd1#syncd: SAI_LOG|SAI_API_SWITCH: punt packet parsing failed
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
In Cisco platforms these error messages should be warning instead of error messages. We will be making the change but in the meanwhile, I am adding an ignore in log analyzer ignore files to avoid causing testcase failures
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation