[action] [PR:12849] Ignore error log from ctrmgrd in test_k8s_config_patch_apply#12858
Merged
mssonicbld merged 1 commit intosonic-net:202311from May 16, 2024
Merged
Conversation
8 tasks
Collaborator
Author
|
Original PR: #12849 |
Collaborator
Author
|
/azp run Azure.sonic-mgmt |
|
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
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 case
test_k8s_config_patch_applyis error out because error logs in syslog. The error message is expected as DUT doesn't have public DNS access.This PR addressed the issue by ignoring the error log.
Type of change
Back port request
Approach
What is the motivation for this PR?
This PR is to ignore error log from ctrmgrd in
test_k8s_config_patch_apply.How did you do it?
Add the expected log pattern into ignore list of LogAnalyzer.
How did you verify/test it?
Verified by running the test in a physical testbed. The test can pass now.
Any platform specific information?
No.
Supported testbed topology if it's a new test case?
Not a new test case.
Documentation