Bls fixes #22
Merged
Bls fixes #22
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
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.
Fixing another way the wrong kernel version will be seen booting after rolling back. This failure mode happens when there is no
saved_entryconfigured in the/boot/grub2/grubenvfile. When this is true, the default boot entry is undefined and index 0 is booted by default. The issue comes when a newer BLS kernel entry has been dropped under the/boot/loader/entriesdirectory making it the new default. To get around this, we add a saved_entry configuration to grubenv if it doesn't already exist before creating the boot backup and snapshots.