connectivity: Add "Link not found" in the exception list #2341
Conversation
This file contains 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
michi-covalent
force-pushed
the
pr/michi/exception-struggle
branch
from
be5680e to
9f5dcc2
Compare
michi-covalent
force-pushed
the
pr/michi/exception-struggle
branch
from
9f5dcc2 to
542fbb8
Compare
This error shows up frequently, causing the connectivity test to fail. Add the message to the error log exceptions until #1894 is resolved. More specifically, ignore these two messages: level=error msg="Link not found" device=... subsys=datapath-loader level=warning msg="JoinEP: Failed to attach program(s)" error="getting interface by name: Link not found" Signed-off-by: Michi Mutsuzaki <[email protected]>
michi-covalent
force-pushed
the
pr/michi/exception-struggle
branch
from
542fbb8 to
29d5ad0
Compare
|
let's try #2344 first. @tommyp1ckles claims that it might mitigate this issue. |
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.
This error shows up frequently, causing the connectivity test to fail.
Add the message to the error log exceptions until #1894 is resolved.
More specifically, ignore these two messages: