manual-rollbacks: show full roll-back and roll-forward flows #426
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
This expands the section describing permanent rollbacks, in order to make it more explicit how to deal with auto-updates and to show how to manually perform roll-forward steps if required. The scenario came up in a chat thread, and it is good to have the commands written for reference.
|
/cc @travier |
|
Would re-enabling zincati not be enough? Directly rebasing might skip barrier releases? |
|
Yes, well, this gets into the weird territory where intermediate releases (e.g. barriers) may not be working. |
travier
approved these changes
Jul 5, 2022
|
Let's update those once we have something safe in Zincati to specify the version to update too? |
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.
This expands the section describing permanent rollbacks, in order
to make it more explicit how to deal with auto-updates and to show
how to manually perform roll-forward steps if required.
The scenario came up in a chat thread, and it is good to have the
commands written down for reference.