[action] [PR:16077] [Chassis] Reduce wait/timeout time for chassis #16521
+7
−7
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
Description of PR Cisco chassis used to be unstable months ago, so updated the wait time of sshd ready to 600s, and service ready to 900s. After the image became stable, we can reduce the time to: sshd ready: 420s service ready: 600s Will keep monitoring and see whether we can reduce the wait time to align with t0/t1 in the future. Approach What is the motivation for this PR? Cisco chassis used to be unstable months ago, so updated the wait time of sshd ready to 600s, and service ready to 900s. After the image became stable, we can reduce the time to: sshd ready: 420s service ready: 600s Will keep monitoring and see whether we can reduce the wait time to align with t0/t1 in the future. How did you do it? How did you verify/test it? In the nightly test, the configuration works well. Any platform specific information? Supported testbed topology if it's a new test case? Documentation co-authorized by: jianquanye@microsoft.com
|
/azp run |
8 tasks
|
Original PR: #16077 |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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
Cisco chassis used to be unstable months ago, so updated the wait time of sshd ready to 600s, and service ready to 900s.
After the image became stable, we can reduce the time to:
sshd ready: 420s
service ready: 600s
Will keep monitoring and see whether we can reduce the wait time to align with t0/t1 in the future.
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Cisco chassis used to be unstable months ago, so updated the wait time of sshd ready to 600s, and service ready to 900s.
After the image became stable, we can reduce the time to:
sshd ready: 420s
service ready: 600s
Will keep monitoring and see whether we can reduce the wait time to align with t0/t1 in the future.
How did you do it?
How did you verify/test it?
In the nightly test, the configuration works well.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation