LogAnalyzer: Ignore a non-functional error thrown from Linkmgrd#19099
Merged
StormLiangMS merged 1 commit intosonic-net:masterfrom Jul 1, 2025
Merged
LogAnalyzer: Ignore a non-functional error thrown from Linkmgrd#19099StormLiangMS merged 1 commit intosonic-net:masterfrom
StormLiangMS merged 1 commit intosonic-net:masterfrom
Conversation
Adding a regex pattern to ignore the following type of error, ERR mux#linkmgrd: MuxManager.cpp:297 updateProberType: Ethernet140: Unsupported link failure detection type for : software
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
Restart the failed PR test job. |
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Jul 1, 2025
…c-net#19099) What is the motivation for this PR? Loganalyzer was not aware of this newly introduced error message and was failing many of the tests. How did you do it? Added a regex pattern to ignore these errors. How did you verify/test it? By running sonic-mgmt tests.
Collaborator
|
Cherry-pick PR to 202505: #19298 |
11 tasks
yejianquan
pushed a commit
that referenced
this pull request
Jul 2, 2025
…) (#19298) What is the motivation for this PR? Loganalyzer was not aware of this newly introduced error message and was failing many of the tests. How did you do it? Added a regex pattern to ignore these errors. How did you verify/test it? By running sonic-mgmt tests. Co-authored-by: Dhanasekar Rathinavel <[email protected]>
mssonicbld
added
Included in 202505 branch
and removed
Created PR to 202505 branch
labels
nissampa
pushed a commit
to nissampa/sonic-mgmt_dpu_test
that referenced
this pull request
Aug 7, 2025
…c-net#19099) What is the motivation for this PR? Loganalyzer was not aware of this newly introduced error message and was failing many of the tests. How did you do it? Added a regex pattern to ignore these errors. How did you verify/test it? By running sonic-mgmt tests.
ashutosh-agrawal
pushed a commit
to ashutosh-agrawal/sonic-mgmt
that referenced
this pull request
Aug 14, 2025
…c-net#19099) What is the motivation for this PR? Loganalyzer was not aware of this newly introduced error message and was failing many of the tests. How did you do it? Added a regex pattern to ignore these errors. How did you verify/test it? By running sonic-mgmt tests.
vidyac86
pushed a commit
to vidyac86/sonic-mgmt
that referenced
this pull request
Oct 23, 2025
…c-net#19099) What is the motivation for this PR? Loganalyzer was not aware of this newly introduced error message and was failing many of the tests. How did you do it? Added a regex pattern to ignore these errors. How did you verify/test it? By running sonic-mgmt tests.
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
…c-net#19099) What is the motivation for this PR? Loganalyzer was not aware of this newly introduced error message and was failing many of the tests. How did you do it? Added a regex pattern to ignore these errors. How did you verify/test it? By running sonic-mgmt tests. Signed-off-by: opcoder0 <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
…c-net#19099) What is the motivation for this PR? Loganalyzer was not aware of this newly introduced error message and was failing many of the tests. How did you do it? Added a regex pattern to ignore these errors. How did you verify/test it? By running sonic-mgmt tests. Signed-off-by: Guy Shemesh <[email protected]>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
…c-net#19099) What is the motivation for this PR? Loganalyzer was not aware of this newly introduced error message and was failing many of the tests. How did you do it? Added a regex pattern to ignore these errors. How did you verify/test it? By running sonic-mgmt tests. Signed-off-by: Aharon Malkin <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
…c-net#19099) What is the motivation for this PR? Loganalyzer was not aware of this newly introduced error message and was failing many of the tests. How did you do it? Added a regex pattern to ignore these errors. How did you verify/test it? By running sonic-mgmt tests. Signed-off-by: Guy Shemesh <[email protected]>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Jan 13, 2026
…c-net#19099) What is the motivation for this PR? Loganalyzer was not aware of this newly introduced error message and was failing many of the tests. How did you do it? Added a regex pattern to ignore these errors. How did you verify/test it? By running sonic-mgmt tests.
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
…c-net#19099) What is the motivation for this PR? Loganalyzer was not aware of this newly introduced error message and was failing many of the tests. How did you do it? Added a regex pattern to ignore these errors. How did you verify/test it? By running sonic-mgmt tests. Signed-off-by: Guy Shemesh <[email protected]>
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Feb 2, 2026
…c-net#19099) What is the motivation for this PR? Loganalyzer was not aware of this newly introduced error message and was failing many of the tests. How did you do it? Added a regex pattern to ignore these errors. How did you verify/test it? By running sonic-mgmt tests. Signed-off-by: Yael Tzur <[email protected]>
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
Whenever CFG_MUX_CABLE_TABLE_NAME is updated we get the following error,
2025 Jun 15 22:30:03.459694 gd272 ERR mux#linkmgrd: MuxManager.cpp:297 updateProberType: Ethernet140: Unsupported link failure detection type for : software
This is a regression caused by PR : sonic-net/sonic-linkmgrd#288.
This is not causing any functionality breakage. But log analyzer reports this new error and hence the testcase fails.
Since there is no functionality impact, we have added this error message to the list of ignored patterns.
Summary:
Fixes #
https://github.com/aristanetworks/sonic-qual.msft/issues/624
sonic-net/sonic-linkmgrd#301
Type of change
Back port request
Approach
What is the motivation for this PR?
Loganalyzer was not aware of this newly introduced error message and was failing many of the tests.
How did you do it?
Added a regex pattern to ignore these errors.
How did you verify/test it?
By running sonic-mgmt tests.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation