[action] [PR:20049] [Arista] Ignore SRV6 ERR log on Arista platforms#20052
Merged
mssonicbld merged 1 commit intosonic-net:202505from Aug 4, 2025
Merged
[action] [PR:20049] [Arista] Ignore SRV6 ERR log on Arista platforms#20052mssonicbld merged 1 commit intosonic-net:202505from
mssonicbld merged 1 commit intosonic-net:202505from
Conversation
What is the motivation for this PR? Ignore SRV6 ERR in loganalyzer. How did you do it? Ignore SRV6 ERR in loganalyzer. How did you verify/test it? Verified by testcase test_lldp_syncd.py on Arista-720DT Mx:
11 tasks
Collaborator
Author
|
Original PR: #20049 |
Collaborator
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
…net#20052)" This reverts commit 93f3cad.
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
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:
We got below loganalyzer failure on latest Arista images. Since this ERR log is only for SRV6, I ignore them in loganalyzer:
Type of change
Back port request
Approach
What is the motivation for this PR?
Ignore SRV6 ERR in loganalyzer.
How did you do it?
Ignore SRV6 ERR in loganalyzer.
How did you verify/test it?
Verified by testcase
test_lldp_syncd.pyon Arista-720DT Mx:Any platform specific information?
Arista.
Supported testbed topology if it's a new test case?
Documentation