Fix ansible timed out for last boot time check 600 #244
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
lilyeyes
force-pushed
the
fix-ansible-Timed-out-for-last-boot-time-check-600
branch
5 times, most recently
from
37ec885 to
4f8ef96
Compare
mpagot
reviewed
Jun 24, 2024
a-kpappas
approved these changes
Jun 24, 2024
Fix sporadic HANA reboot timeout in qe-sap-deployment Ansible TEAM-8893 - Follow up to sporadic HANA reboot timeout in qe-sap-deployment Ansible
lilyeyes
force-pushed
the
fix-ansible-Timed-out-for-last-boot-time-check-600
branch
from
4f8ef96 to
2c52744
Compare
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.
Fix ansible timed out for last boot time check
Related ticket: TEAM-8893 - Follow up to sporadic HANA reboot timeout in qe-sap-deployment Ansible
FYI:
connect_timeout:
Maximum seconds to wait for a successful connection to the managed hosts before trying again.
If unspecified, the default setting for the underlying connection plugin is used.
(See https://docs.ansible.com/ansible/latest/collections/ansible/builtin/reboot_module.html)
VRs: tried 20+ times and this timed out issue disappears.
https://openqa.suse.de/tests/14714474#next_previous