SNMP link-local test: wait until snmp agent fully start #16461
Merged
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
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Blueve
approved these changes
Jan 13, 2025
wangxin
approved these changes
Jan 13, 2025
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Jan 13, 2025
) What is the motivation for this PR? On Nokia-7215 platform, we observed below flaky failure: Timeout: No Response from fe80::xxxx%eth0. The root cause is that Nokia-7215 has low performance and the snmpget command is issued before snmpagent fully start. How did you do it? To resolve this issue, I added a wait_until to ensure snmpagent already listening on the link-local IP address. How did you verify/test it? Verified on Nokia-7215 Mx testbed.
|
Cherry-pick PR to 202411: #16481 |
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Jan 13, 2025
) What is the motivation for this PR? On Nokia-7215 platform, we observed below flaky failure: Timeout: No Response from fe80::xxxx%eth0. The root cause is that Nokia-7215 has low performance and the snmpget command is issued before snmpagent fully start. How did you do it? To resolve this issue, I added a wait_until to ensure snmpagent already listening on the link-local IP address. How did you verify/test it? Verified on Nokia-7215 Mx testbed.
12 tasks
|
Cherry-pick PR to 202405: #16482 |
12 tasks
mssonicbld
pushed a commit
that referenced
this pull request
Jan 13, 2025
What is the motivation for this PR? On Nokia-7215 platform, we observed below flaky failure: Timeout: No Response from fe80::xxxx%eth0. The root cause is that Nokia-7215 has low performance and the snmpget command is issued before snmpagent fully start. How did you do it? To resolve this issue, I added a wait_until to ensure snmpagent already listening on the link-local IP address. How did you verify/test it? Verified on Nokia-7215 Mx testbed.
mssonicbld
pushed a commit
that referenced
this pull request
Jan 13, 2025
What is the motivation for this PR? On Nokia-7215 platform, we observed below flaky failure: Timeout: No Response from fe80::xxxx%eth0. The root cause is that Nokia-7215 has low performance and the snmpget command is issued before snmpagent fully start. How did you do it? To resolve this issue, I added a wait_until to ensure snmpagent already listening on the link-local IP address. How did you verify/test it? Verified on Nokia-7215 Mx testbed.
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:
On Nokia-7215 platform, we observed below flaky failure:
The root cause is that Nokia-7215 has low performance and the
snmpgetcommand is issued before snmpagent fully start.To resolve this issue, I added a wait_until to ensure snmpagent already listening on the link-local IP address.
Type of change
Back port request
Approach
What is the motivation for this PR?
On Nokia-7215 platform, we observed below flaky failure:
The root cause is that Nokia-7215 has low performance and the
snmpgetcommand is issued before snmpagent fully start.How did you do it?
To resolve this issue, I added a wait_until to ensure snmpagent already listening on the link-local IP address.
How did you verify/test it?
Verified on Nokia-7215 Mx testbed.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation