Use timeout to kill vrnetlab readiness check SSH sessions #1734
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
The SSH client used to check vrnetlab readiness can be stuck for an awfully long when the VM is in just the right phase of getting ready. This change uses the 'timeout' command (when available) to kill the check after 5 seconds, allowing the Ansible retry mechanism to work as expected.
ssasso
approved these changes
Jan 3, 2025
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.
The SSH client used to check vrnetlab readiness can be stuck for an awfully long when the VM is in just the right phase of getting ready. This change uses the 'timeout' command (when available) to kill the check after 5 seconds, allowing the Ansible retry mechanism to work as expected.