[master][sonic-mgmt]: Add LogAnalyzer ignore pattern for SAI FEC stat error#23304
Open
ashishalok-arista wants to merge 1 commit intosonic-net:masterfrom
Open
[master][sonic-mgmt]: Add LogAnalyzer ignore pattern for SAI FEC stat error#23304ashishalok-arista wants to merge 1 commit intosonic-net:masterfrom
ashishalok-arista wants to merge 1 commit intosonic-net:masterfrom
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: ashish.alok <[email protected]>
ashishalok-arista
force-pushed
the
master-ignore-syslog-fec-stat-err
branch
from
9791926 to
58188fc
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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:
test_pfcwd_cli (and other tests using LogAnalyzer) began failing from the March 6, 2026 SAI upgrade (14.1.x → 14.3.x). The upgrade promoted FEC stat failure log messages from INFO to ERROR level, making them visible to LogAnalyzer.
These ERR messages appear ~40 seconds after syncd starts, during FlexCounter's initial counter discovery poll.
Tests that run
config reload -y -fas part of setup/teardown restart syncd, triggering a fresh poll cycle each time. Each reload produces a burst of FEC error messages, which LogAnalyzer flags as unexpected.The existing ignore pattern targets the old message format (failed with error Feature unavailable) and does not match the current format (failed - port: , rc: -16).
Fixes: qual-issue
Type of change
Back port request
Approach
What is the motivation for this PR?
The SAI upgrade promoted FEC stat failure log messages from INFO to ERROR level, making them visible to LogAnalyzer. These messages appear ~40 seconds after syncd starts during FlexCounter's initial counter discovery poll. Tests that run config reload as part of setup/teardown restart syncd, triggering a fresh poll cycle each time and producing a burst of ERR messages that LogAnalyzer flags as unexpected. The existing ignore pattern no longer matches the current message format.
How did you do it?
Added a LogAnalyzer ignore pattern matching the current message format:
r".* ERR syncd\d*#syncd.*SAI_API_PORT:_brcm_sai_read_fec_stat_err_counters.* failed - port: \d+, rc: -16.*"How did you verify/test it?
Confirmed the pattern matches the ERR messages observed in the failing test logs.
Any platform specific information?
Applies to broadcom-based platforms
Supported testbed topology if it's a new test case?
Documentation