ipv6_fixture needs to wait for all services to be up#13213
Merged
yejianquan merged 1 commit intosonic-net:masterfrom Jun 11, 2024
Merged
ipv6_fixture needs to wait for all services to be up#13213yejianquan merged 1 commit intosonic-net:masterfrom
yejianquan merged 1 commit intosonic-net:masterfrom
Conversation
sdszhang
added
Request for 202305 branch
Request for 202311 branch
Issue for 202311
and removed
Issue for 202311
labels
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Jun 12, 2024
Description of PR Summary: Fixes MSFT ADO 28332318 Approach What is the motivation for this PR? Fix case error with the following error message: failed on setup with "Failed: <ipv6 address> not appeared in xxx netstat" On some physical testbed, the snmpd process took around 3 minutes to come up. Current convert_and_restore_config_db_to_ipv6_only needs to check all process to be up before proceeding with SNMP checking. How did you do it? wait_critical_processes() checks for the critical process which includes snmpd. How did you verify/test it? Tested it locally. co-authorized by: jianquanye@microsoft.com
Collaborator
|
@sdszhang PR conflicts with 202311 branch |
Collaborator
|
Cherry-pick PR to 202405: #13237 |
Collaborator
|
@sdszhang PR conflicts with 202305 branch |
8 tasks
This was referenced Jun 12, 2024
mssonicbld
pushed a commit
that referenced
this pull request
Jun 12, 2024
Description of PR Summary: Fixes MSFT ADO 28332318 Approach What is the motivation for this PR? Fix case error with the following error message: failed on setup with "Failed: <ipv6 address> not appeared in xxx netstat" On some physical testbed, the snmpd process took around 3 minutes to come up. Current convert_and_restore_config_db_to_ipv6_only needs to check all process to be up before proceeding with SNMP checking. How did you do it? wait_critical_processes() checks for the critical process which includes snmpd. How did you verify/test it? Tested it locally. co-authorized by: jianquanye@microsoft.com
mssonicbld
added
Included in 202405 branch
and removed
Created PR to 202405 branch
labels
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
3 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
Summary:
Fixes MSFT ADO 28332318
Type of change
Back port request
Approach
What is the motivation for this PR?
Fix case error with the following error message:
failed on setup with "Failed: <ipv6 address> not appeared in xxx netstat"On some physical testbed, the snmpd process took around 3 minutes to come up.
Current convert_and_restore_config_db_to_ipv6_only needs to check all process to be up before proceeding with SNMP checking.
How did you do it?
wait_critical_processes() checks for the critical process which includes snmpd.
How did you verify/test it?
Tested it locally.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation