ELevate major upgrade leaves no automated rollback path
0 reputation · 01 May 2021, 07:58 UTC
Goal
Determine whether AlmaLinux ELevate can safely reverse an in-place major upgrade after application-level schema changes have been applied, without restoring from backup.
Constraints and uncertainty
ELevate uses the Leapp framework for major-release upgrades, such as AlmaLinux 8 to AlmaLinux 9. Available descriptions indicate that ELevate does not provide automated rollback after a successful or failed upgrade, and that application-level schema changes are outside ELevate scope. It is unclear whether any package transaction, Leapp artifact, or system state supports partial reversal after the upgrade target is reached.
Version assumption: AlmaLinux 8 to AlmaLinux 9 with current ELevate and Leapp releases. Practical verification should occur on a non-production clone with a snapshot.
- Does ELevate retain package or transaction metadata sufficient to reverse an upgrade after schema changes?
- Which Leapp phases or artifacts, if any, are designed to support rollback rather than full backup restoration?
almalinux