Repository navigation
elevate: Document that Secure Boot must be disabled for cross-vendor upgrades - #884
Merged
Merged
Conversation
…upgrades With Secure Boot enabled, the upgrade entry fails to boot with "invalid signature" when the target OS comes from a different vendor than the installed one (e.g. CentOS 7 to AlmaLinux 8): the upgrade kernel is signed by the target OS vendor, while the system is still started by the shim of the installed OS. Add a Frequent Issues section with the error, the explanation, the workaround (disable Secure Boot for the upgrade) and how to recover after a failed reboot. Note that upgrades from EL8 and EL9 based systems are inhibited by leapp in this case, while the CentOS 7 path has no such check. Add a warning to the Requirements of the Quickstart Guide. Related: AlmaLinux/leapp-repository#159
andrewlukoshko
approved these changes
Nov 12, 2026
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
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.
With Secure Boot enabled, the
ELevate-Upgrade-Initramfsentry fails to boot withinvalid signaturewhen the target OS comes from a different vendor than the installed one, for example CentOS 7 to AlmaLinux 8. The upgrade kernel is signed by the target OS vendor, while the system is still started by the shim of the installed OS.Changes:
leapp preupgrade, while the CentOS 7 path has no such check.Related: AlmaLinux/leapp-repository#159