mantle/kola: increase reboot wait time for fcos.upgrade.basic #3883
Conversation
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
We've been seeing this fail a lot more on AWS recently and we think
it's because we're bumping up into this timeout. The truth is that
we're not just waiting for a reboot here, but actually waiting for
zincati to select the upgrade, for rpm-ostree to deploy it, finalize
and reboot. Given all that I can see why this might be bumping up
into the limit.
```
=== RUN fcos.upgrade.basic
=== RUN fcos.upgrade.basic/setup
=== RUN fcos.upgrade.basic/upgrade-from-previous
=== RUN fcos.upgrade.basic/upgrade-from-current
--- FAIL: fcos.upgrade.basic (495.26s)
--- PASS: fcos.upgrade.basic/setup (204.18s)
cluster.go:162: real 0m0.045s
cluster.go:162: user 0m0.006s
cluster.go:162: sys 0m0.012s
--- FAIL: fcos.upgrade.basic/upgrade-from-previous (122.05s)
basic.go:347: failed waiting for machine reboot: timed out after 2m0s waiting for machine to reboot
--- SKIP: fcos.upgrade.basic/upgrade-from-current (0.00s)
cluster.go:54: A previous test has already failed
```
jlebon
approved these changes
Sep 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
We've been seeing this fail a lot more on AWS recently and we think it's because we're bumping up into this timeout. The truth is that we're not just waiting for a reboot here, but actually waiting for zincati to select the upgrade, for rpm-ostree to deploy it, finalize and reboot. Given all that I can see why this might be bumping up into the limit.