[action] [PR:12174] Ignore error messages when querying debug counter#12282
Merged
mssonicbld merged 1 commit intosonic-net:202311from Apr 3, 2024
Merged
[action] [PR:12174] Ignore error messages when querying debug counter#12282mssonicbld merged 1 commit intosonic-net:202311from
mssonicbld merged 1 commit intosonic-net:202311from
Conversation
Signed-off-by: Lawrence Lee <[email protected]>
8 tasks
Collaborator
Author
|
Original PR: #12174 |
This file contains hidden or 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
2 participants
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)
Type of change
Back port request
Approach
What is the motivation for this PR?
Some test cases involving creating/deleting debug counters fail the log analyzer due to the below message:
This is because there is a short transient period (1-2 sec) after the counter is deleted where the device is still trying to get the counter stats. Once the system becomes stable again the error messages stop.
See ADO 26161007
How did you do it?
Add this message to the loganalyzer common ignore list
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation