AlmaLinux Wiki
# last updated: 2025-01-30

# ELevate NG Testing Guide

WARNING

Before beginning, we HIGHLY recommend that you follow system administration best practices and make sure you have backups and/or snapshots of your system before you proceed. It is recommended to do a trial run in a sandbox to verify the upgrade worked as expected before you attempt to upgrade any production system. Please report any issues encountered to the AlmaLinux Bug Tracker (opens new window) and/or AlmaLinux Chat Migration Channel (opens new window)

The ELevate NG supports a number of 3rd party repositories:

  • EPEL support is currently available for upgrades to AlmaLinux OS.
    • EPEL support is also available for upgrades to AlmaLinux OS 10.0 beta. lease, note, that the support works only for those packages from EL 9 that are currently available for EL 10. Unavailable packages from EL 9 will remain on the system after the upgrade.
  • Docker CE - for all supported operating systems including AlmaLinux OS 10.0 beta.
  • MariaDB - for all supported operating systems.
  • Microsoft Linux Package Repositories - for all supported operating systems.
  • nginx - for all supported operating systems.
  • PostgreSQL - for all supported operating systems.
  • Imunify - for upgrades to EL 8.
  • KernelCare - for all supported operating systems.

TIP

You can add more 3rd party repositories support. See more on the Contribute page.

Currently, the following upgrade paths are available:

image

* - upgrading from Scientific Linux 7 to AlmaLinux 8 requires a workaround. Please, see more in the known issues.
** - upgrading to Oracle Linux 9 is available with the Oracle Leapp utility (opens new window) and will not be supported by ELevate project.
*** - Upgrade to AlmaLinux OS 10 is only available to the version 10.0 Beta. Currently, it doesn't have support for x86_64_v2.

# Upgrade CentOS 7 to AlmaLinux 8

  • Update the system to get the latest updates and reboot your machine. NOTE: Since the CentOS 7 repositories are now offline you will need to swap to the CentOS vault, or you can use our CentOS 7 mirror that we've setup for use with ELevate:

    sudo curl -o /etc/yum.repos.d/CentOS-Base.repo https://el7.repo.almalinux.org/centos/CentOS-Base.repo
sudo yum upgrade -y
sudo reboot

  • Install ELevate NG version repo config for CentOS7, and import ELevate GPG key:

    sudo curl -o /etc/yum.repos.d/elevate-ng.repo https://repo.almalinux.org/elevate/testing/elevate-ng-el$(rpm -E %rhel).repo
sudo rpm --import https://repo.almalinux.org/elevate/RPM-GPG-KEY-ELevate

  • Install leapp packages and upgrade data for AlmaLinux:

    sudo yum install -y leapp-upgrade leapp-data-almalinux

  • Start a preupgrade check. In the meanwhile, the Leapp utility creates a special /var/log/leapp/leapp-report.txt file that contains possible problems and recommended solutions. No rpm packages will be installed at this phase.

    WARNING

    Preupgrade check will fail as the default install doesn't meet all requirements for the upgrade.

    sudo leapp preupgrade

    This summary report will help you get a picture of whether it is possible to continue the upgrade.

    TIP

    In certain configurations, Leapp generates /var/log/leapp/answerfile with true/false questions. Leapp utility requires answers to all these questions in order to proceed with the upgrade.

  • The following fixes from the /var/log/leapp/leapp-report.txt file are the most popular for CentOS 7, but it's recommended to review the whole file.

    sudo rmmod pata_acpi
echo PermitRootLogin yes | sudo tee -a /etc/ssh/sshd_config
sudo leapp answer --section remove_pam_pkcs11_module_check.confirm=True

    Check the ELevate Frequent Issues page for known and frequent issues and guidance steps to solve them.

  • Start an upgrade. You'll be offered to reboot the system after this process is completed.

    sudo leapp upgrade
sudo reboot

  • A new entry in GRUB called ELevate-Upgrade-Initramfs will appear. The system will be automatically booted into it. See how the upgrade process goes in the console.

  • After reboot, login to the system and check how the upgrade went. Verify that the current OS is the one you need. Check logs and packages left from the previous OS version, consider removing them or upgrading them manually.

    cat /etc/redhat-release
cat /etc/os-release
rpm -qa | grep el7 
sudo cat /var/log/leapp/leapp-report.txt
sudo cat /var/log/leapp/leapp-upgrade.log

# Prepare the system for upgrade to AlmaLinux 9

When successfully upgraded to AlmaLinux 8 OS, consider performing these steps to prepare your system for upgrading to AlmaLinux 9:

  • Navigate to the /etc/ directory and use an editor of your choice to edit the yum.conf file. You need to remove everything from the exclude line especially that refers to elevate or leapp.

    # An example of yum.conf file:
    [main]
gpgcheck=1
installonly_limit=3
clean_requirements_on_remove=True
best=True
skip_if_unavailable=False
exclude=python2-leapp,snactor,leapp-upgrade-el7toel8,leapp

  • Then navigate to the /etc/dnf/ directory and use an editor of your choice to do the same in the dnf.conf file.

  • Now you can remove/manually upgrade packages left from CentOS 7 without any conflicts.

  • Check packages left from CentOS 7:

    rpm -qa | grep el7

    An example output with a list of packages:

     python2-leapp-0.16.0-2.el7.noarch
 kernel-3.10.0-1160.105.1.el7.x86_64
 leapp-upgrade-el7toel8-0.19.0-5.el7.noarch
 leapp-data-almalinux-0.2-6.el7.noarch
 leapp-0.16.0-2.el7.noarch

    As mentioned above, consider removing these packages or upgrading them manually to proceed with the upgrade to AlmaLinux 9.

    TIP

    If you face difficulties while removing the packages, the following command might help you:

    sudo rpm -e --nodeps <package_name>

  • You can also check for the packages left from the upgrade process and remove them:

    rpm -qa | grep elevate
rpm -qa | grep leapp

  • Check whether you have the /root/tmp_leapp_py3 directory created and if so delete it.

    sudo rm -fr /root/tmp_leapp_py3

  • Clean up your machine.

    sudo dnf clean all

  • You may also have to remove old RSA/SHA1 GPG keys. List the keys:

    rpm -q gpg-pubkey --qf '%{NAME}-%{VERSION}-%{RELEASE}\t%{SUMMARY}\n'

    To remove them, use use the rpm -e command:

    sudo rpm -e [keyname]

After these preparations are completed, you can upgrade your AlmaLinux 8 machine to AlmaLinux 9.

# Upgrading AlmaLinux 8 to AlmaLinux 9

  • Install ELevate NG version repo config for AlmaLinux8:

    sudo curl -o /etc/yum.repos.d/elevate-ng.repo https://repo.almalinux.org/elevate/testing/elevate-ng-el$(rpm -E %rhel).repo

  • Install leapp packages and upgrade data for AlmaLinux which is target OS:

    sudo yum install -y leapp-upgrade leapp-data-almalinux

  • Start a preupgrade check. In the meanwhile, the Leapp utility creates a special /var/log/leapp/leapp-report.txt file that contains possible problems and recommended solutions. No rpm packages will be installed at this phase.

    WARNING

    Preupgrade check will fail as the default install doesn't meet all requirements for the upgrade.

    sudo leapp preupgrade

    This summary report will help you get a picture of whether it is possible to continue the upgrade.

    TIP

    In certain configurations, Leapp generates /var/log/leapp/answerfile with true/false questions. Leapp utility requires answers to all these questions in order to proceed with the upgrade.

  • The following fixes from the /var/log/leapp/leapp-report.txt file are the most popular fixes for RHEL8-based operating systems:

    sudo sed -i "s/^AllowZoneDrifting=.*/AllowZoneDrifting=no/" /etc/firewalld/firewalld.conf
sudo leapp answer --section check_vdo.confirm=True

    You might also find the following issue in the leapp-report file that can interfere with the upgrade. Consider removing the file:

     Network configuration for unsupported device types detected
 Summary: RHEL 9 does not support the legacy network-scripts package that was deprecated in RHEL 8 in favor of NetworkManager. Files for device types that are not supported by NetworkManager are present in the system. Files with the problematic configuration:
   - /etc/sysconfig/network-scripts/ifcfg-eth0

    Check the ELevate Frequent Issues page for known and frequent issues and guidance steps to solve them.

  • Start an upgrade. You'll be offered to reboot the system after this process is completed.

    sudo leapp upgrade
sudo reboot

    TIP

    You might want to remove the make-devel package as it conflicts when running leapp upgrade and thus this step fails.

  • A new entry in GRUB called ELevate-Upgrade-Initramfs will appear. The system will be automatically booted into it. See how the upgrade process goes in the console.

  • After reboot, login to the system and check how the upgrade went. Verify that the current OS is the one you need. Check logs and packages left from the previous OS version, consider removing them or upgrade them manually.

    cat /etc/redhat-release
cat /etc/os-release
rpm -qa | grep el8
sudo cat /var/log/leapp/leapp-report.txt
sudo cat /var/log/leapp/leapp-upgrade.log

# Prepare the system for upgrade to AlmaLinux 10

When successfully upgraded to AlmaLinux 9 OS, consider performing these steps to prepare your system for upgrading to AlmaLinux 10:

  • Navigate to the /etc/ directory and use an editor of your choice to edit the yum.conf file. You need to remove everything from the exclude line especially that refers to elevate or leapp.

    # An example of yum.conf file:
    [main]
gpgcheck=1
installonly_limit=3
clean_requirements_on_remove=True
best=True
skip_if_unavailable=False
exclude=python2-leapp,snactor,leapp-upgrade-el8toel9,leapp

  • Then navigate to the /etc/dnf/ directory and use an editor of your choice to do the same in the dnf.conf file.

  • Now you can remove/manually upgrade packages left from AlmaLinux 8 without any conflicts.

  • Check packages left from AlmaLinux 8:

    rpm -qa | grep el8

    An example output with a list of packages:

     kernel-modules-4.18.0-553.32.1.el8_10.x86_64
 leapp-0.18.0-2.el8.noarch
 leapp-data-almalinux-0.5-1.el8.20241127.noarch
 kernel-core-4.18.0-553.32.1.el8_10.x86_64
 kernel-4.18.0-553.32.1.el8_10.x86_64
 python3-leapp-0.18.0-2.el8.noarch
 leapp-upgrade-el8toel9-0.21.0-4.el8.elevate.5.noarch

    As mentioned above, consider removing these packages or upgrading them manually to proceed with the upgrade to AlmaLinux 10.

    TIP

    If you face difficulties while removing the packages, the following command might help you:

    sudo rpm -e --nodeps <package_name>

  • You can also check for the packages left from the upgrade process and remove them:

    rpm -qa | grep elevate
rpm -qa | grep leapp

  • Check whether you have the /root/tmp_leapp_py3 directory created and if so delete it.

    sudo rm -fr /root/tmp_leapp_py3

  • Clean up your machine.

    sudo dnf clean all

After these preparations are completed, you can upgrade your AlmaLinux 9 machine to AlmaLinux 10.

# Upgrading AlmaLinux 9 to AlmaLinux 10

WARNING

This upgrade is currently in development and testing. The main goals are to deliver working leapp-data and leapp-repository packages needed for the upgrade and to be able to upgrade to AlmaLinux OS 10 successfully. This upgrade is not recommended for production machines.

TIP

These steps can also be used to perform the upgrade from CentOS Stream 9 to CentOS Stream 10. The only difference is the leapp-data package.

  • Install ELevate NG version repo config for AlmaLinux 9:

    sudo curl -o /etc/yum.repos.d/elevate-ng.repo https://repo.almalinux.org/elevate/testing/elevate-ng-el$(rpm -E %rhel).repo

  • Import ELevate GPG key:

    sudo rpm --import https://repo.almalinux.org/elevate/RPM-GPG-KEY-ELevate

  • Install leapp packages and upgrade data for AlmaLinux which is target OS:

    sudo yum install -y leapp-upgrade leapp-data-almalinux

    TIP

    For the upgrade to CentOS Stream 10, please, use the leapp-data-centos package:

    sudo yum install -y leapp-upgrade leapp-data-centos

  • Start a preupgrade check. In the meanwhile, the Leapp utility creates a special /var/log/leapp/leapp-report.txt file that contains possible problems and recommended solutions. No rpm packages will be installed at this phase.

    WARNING

    Preupgrade check will fail as the default install doesn't meet all requirements for the upgrade.

    sudo leapp preupgrade

    This summary report will help you get a picture of whether it is possible to continue the upgrade.

    TIP

    In certain configurations, Leapp generates /var/log/leapp/answerfile with true/false questions. Leapp utility requires answers to all these questions in order to proceed with the upgrade.

  • Currently, the direct upgrade from Almalinux OS 9 to AlmaLinux OS 10.0 Beta goes smoothly. If there is a progressive upgrade from CentOS 7 to AlmaLinux OS 10.0 Beta, please check the known issues section.

    TIP

    For CentOS Stream 9 to CentOS Stream 10 upgrade, please, also see the known issues section.

  • Start an upgrade. You'll be offered to reboot the system after this process is completed.

    sudo leapp upgrade
sudo reboot

  • A new entry in GRUB called ELevate-Upgrade-Initramfs will appear. The system will be automatically booted into it. See how the upgrade process goes in the console.

  • After reboot, login to the system and check how the upgrade went. Verify that the current OS is the one you need. Check logs and packages left from the previous OS version, consider removing them or upgrade them manually.

    cat /etc/redhat-release
cat /etc/os-release
rpm -qa | grep el9
sudo cat /var/log/leapp/leapp-report.txt
sudo cat /var/log/leapp/leapp-upgrade.log

# Demo Video

Here we have provided a demo of a CentOS 7.x to AlmaLinux 8.x upgrade using the AlmaLinux ELevate Project.

# Known Issues

# Upgrading from Scientific Linux 7

Upgrading from Scientific Linux 7 to AlmaLinux 8 requires a workaround. You can apply it by running the following command before the preupgrade check:

rm -rf /usr/share/redhat-release /usr/share/doc/redhat-release

# Progressive upgrade to AlmaLinux 10.0 Beta

If the system has been progressively upgraded from CentOS 7, the following issues appear after the preupgrade check when upgrading AlmaLinux 9 to AlmaLinux 10.0 Beta. The issues can be found in the generated /var/log/leapp/leapp-report.txt file.

  • "Deprecated DHCP plugin configured" inhibitor.
    • To mitigate the "Deprecated DHCP plugin configured" inhibitor, run:
      # sudo nmcli conn migrate
# sudo nmcli connection modify <connection_name> ipv4.dhcp-timeout 30 ipv6.dhcp-timeout 30
# sudo sed -i'.bak' 's/^dhcp=dhclient//g' /usr/lib/NetworkManager/conf.d/10-dhcp-dhclient.conf
# sudo systemctl restart NetworkManager
    • After that, verify the networking configuration:
      # NetworkManager --print-config
  • "dracut module 'network-legacy' cannot be found or installed." error.
    • To fix this issue delete the drop-in:
      # sudo rm -f /etc/dracut.conf.d/50-network-legacy.conf
  • Before rebooting, make sure you have a working main console. You will probably need to check the /etc/default/grub. An example of the console-related settings:
    GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="console=ttyS0,115200 console=tty0"

# Upgrade from CentOS Strem 9 to CentOS Stream 10

During CentOS Stream 9 to CentOS Stream 10 upgrade the following error can appear during preupgrade/upgrade step and can also be found in the generated /var/log/leapp/leapp-report.txt file:

error: Verifying a signature using certificate 99DB70FAE1D7CE227FB6488205B555B38483C65D (CentOS (CentOS Official Signing Key) <security@centos.org>)

To fix the error, please, manually remove and import the CentOS GPG Key using the following commands:

rpm -e gpg-pubkey-8483c65d-5ccc5b19
rpm --import https://www.centos.org/keys/RPM-GPG-KEY-CentOS-Official-SHA256

# Get Help

Report your feedback to AlmaLinux ~Migration Channel (opens new window). We're especially interested in packages left from the previous OS versions. This information will allow us to improve ELevate's configuration files.

← ELevate Frequent Issues →