Ignore error messages when querying debug counter#12174
Merged
bingwang-ms merged 1 commit intosonic-net:masterfrom Apr 1, 2024
Merged
Ignore error messages when querying debug counter#12174bingwang-ms merged 1 commit intosonic-net:masterfrom
bingwang-ms merged 1 commit intosonic-net:masterfrom
Conversation
theasianpianist
force-pushed
the
ignore-debug-log
branch
from
418150e to
73ee00b
Compare
Signed-off-by: Lawrence Lee <[email protected]>
theasianpianist
force-pushed
the
ignore-debug-log
branch
from
73ee00b to
87e39ee
Compare
bpar9
approved these changes
Mar 28, 2024
prsunny
approved these changes
Apr 1, 2024
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Apr 2, 2024
Signed-off-by: Lawrence Lee <[email protected]>
Collaborator
|
Cherry-pick PR to 202311: #12282 |
8 tasks
mssonicbld
pushed a commit
that referenced
this pull request
Apr 3, 2024
Signed-off-by: Lawrence Lee <[email protected]>
mssonicbld
added
Included in 202311 branch
and removed
Created PR to 202311 branch
labels
veronica-arista
added a commit
to veronica-arista/sonic-mgmt
that referenced
this pull request
Dec 14, 2024
Similar issue to sonic-net#12174 in that counters stats continue to be polled in an unstable state. In the test_iface_namingmode.py case, TestConfigInterface resets the interface configurations at the end, and these syslog errors only appear after the test begins the teardown process. Adding a loganalyzer ignore for this message to this test to fix.
8 tasks
rlhui
pushed a commit
that referenced
this pull request
Mar 2, 2025
Similar issue to #12174 in that counters stats continue to be polled in an unstable state. In the test_iface_namingmode.py case, TestConfigInterface resets the interface configurations at the end, and these syslog errors only appear after the test begins the teardown process. Adding a loganalyzer ignore for this message to this test to fix.
nissampa
pushed a commit
to nissampa/sonic-mgmt_dpu_test
that referenced
this pull request
Mar 4, 2025
Similar issue to sonic-net#12174 in that counters stats continue to be polled in an unstable state. In the test_iface_namingmode.py case, TestConfigInterface resets the interface configurations at the end, and these syslog errors only appear after the test begins the teardown process. Adding a loganalyzer ignore for this message to this test to fix.
nnelluri-cisco
pushed a commit
to nnelluri-cisco/sonic-mgmt
that referenced
this pull request
Mar 15, 2025
Similar issue to sonic-net#12174 in that counters stats continue to be polled in an unstable state. In the test_iface_namingmode.py case, TestConfigInterface resets the interface configurations at the end, and these syslog errors only appear after the test begins the teardown process. Adding a loganalyzer ignore for this message to this test to fix.
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
6 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