[202412][sonic-mgmt] Add loganalyzer regex to ignore sai_query_attribute_capability related errors#766
Merged
sdszhang merged 1 commit intoAzure:202412from Oct 19, 2025
Conversation
…te_capability related errors.
11 tasks
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:
cherry-picking (#20596) to 202412
Fixes # (#807)
Type of change
Back port request
Approach
What is the motivation for this PR?
Add regex to skip sai_query_attribute_capability related loganalyzer errors
How did you do it?
Added 2 regex to loganalyzer_common_ignore.txt file to ignore
non-functional error in swss PR pipeline till
Fix switch capabilities enum query with metadata validation sonic-net/sonic-swss#3866 is merged
fixed from SAI, CS00012422823 is raised
How did you verify/test it?
Tested on Arista-7050X3 running dualtor-aa topology
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation