-
Notifications
You must be signed in to change notification settings - Fork 741
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dhcp_relay] Update error log for dhcp server route incorrect #15898
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 1 out of 1 changed files in this pull request and generated no suggestions.
Comments skipped due to low confidence (1)
tests/dhcp_relay/conftest.py:151
- The phrase "but not it's going through mgmt interface" should be corrected to "but instead it's going through mgmt interface".
"Packets relayed to DHCP server should go through default route via upstream neighbor, but not it's going through mgmt interface, which means device is in a unhealthy status"
f57d308
to
0cf6296
Compare
0cf6296
to
bf7e715
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 suggestion.
179b0da
to
ff2fc5e
Compare
Hi @wangxin could you please help to merge this PR? |
Hi @bingwang-ms could you please help to approve the backport request? |
Hi @yxieca could you please help to approve this backport request? |
…net#15898) Error log for default route incorrect is ambiguous
…net#15898) Error log for default route incorrect is ambiguous
Cherry-pick PR to 202405: #15995 |
Cherry-pick PR to 202311: #15996 |
Error log for default route incorrect is ambiguous
Error log for default route incorrect is ambiguous
…net#15898) Error log for default route incorrect is ambiguous
Cherry-pick PR to 202411: #16215 |
Error log for default route incorrect is ambiguous
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Error log for default route incorrect is ambiguous
How did you do it?
Update the log
How did you verify/test it?
Run test
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation