[Upgrade Details] For critical state transitions, fsync upgrade marker file #3836
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.
What does this PR do?
This PR calls https://pkg.go.dev/os#File.Sync on the Upgrade Marker file when critical upgrade transitions happen.
Why is it important?
In case the Agent immediately crashes (e.g. host loses power) after critical upgrade transitions, these transitions will be persisted to disk in the Upgrade Marker file.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added an entry in./changelog/fragments
using the changelog toolI have added an integration test or an E2E testRelated issues
UPG_WATCHING
for the entire time that the upgrade is being watched #3827 (comment)