fix: detect machine update failures#4921
Draft
rianmcguirefly wants to merge 2 commits into
Draft
Conversation
rianmcguirefly
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Change Summary
What and Why:
Previously, when we gave up on an update and reverted a machine to its previous version (eg. if pulling the image from the registry failed), flyctl saw the machine in the "started" state (the old version still running) and treated the deploy as successful. Health checks would pass against the old image, so users had no indication their new code wasn't deployed.
Affects both
flyctl deploy(in-place updates) and standaloneflyctl machine update.How:
Wait on the new version we're deploying, and confirm the machine version is what we expected after wait succeeds.
Related to:
Documentation