next: deadend 38.20230310.1.0 #667
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
To work around coreos/fedora-coreos-tracker#1441, we'll need to ship an F37-based barrier release that updates the bootloader before updating to F38. Newly-deployed nodes on 38.20230310.1.0 don't need to go through that barrier release, but our Cincinnati graph builder would force it to do so anyway, causing a downgrade from F38 to F37, and that isn't necessarily safe. 38.20230310.1.0 was never rolled out and was only published for three days, so just deadend it, and roll back stream metadata. This effectively reverts b28f0f3.
|
jlebon
approved these changes
Mar 17, 2023
|
Via |
travier
approved these changes
Mar 17, 2023
dustymabe
approved these changes
Mar 17, 2023
34 tasks
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.
To work around coreos/fedora-coreos-tracker#1441, we'll need to ship an F37-based barrier release that updates the bootloader before updating to F38. Newly-deployed nodes on 38.20230310.1.0 don't need to go through that barrier release, but our Cincinnati graph builder would force it to do so anyway, causing a downgrade from F38 to F37, and that isn't necessarily safe. 38.20230310.1.0 was never rolled out and was only published for three days, so just deadend it, and roll back stream metadata.
This effectively reverts b28f0f3.