Retry bootstrapping k3s on failure #353
Merged
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
Signed-off-by: Jorge Prendes <[email protected]>
jprendes
force-pushed
the
k3s-bootstrapping
branch
from
5281842 to
849525e
Compare
devigned
approved these changes
Oct 11, 2023
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.
Sporadically k3s would fail to bootstrap, see
This PR tries to mitigate this by re-bootstrapping k3s when that happens.
This change uses a timeout of 40s for k3s bootstrapping. If that fails, it uninstalls k3s, reinstalls it, and tries again.
This would continue until it succeeds or the CI timeout of 5min is hit.
Note that in the case where the kube-sys pods never show up, simply restarting the systemd service is not enough (I tired this in one of the many many attempts), which indicates that a complete reinstall is a better option.