Chapter 5. Performing the upgrade

Procedure

1. Ensure that you have a full system backup or a virtual machine snapshot. You can use the following backup options:

   • Create a full backup of your system by using the Relax-and-Recover (ReaR) utility. For more information, see Recovering and restoring a system and What is Relax and Recover (ReaR) and how can I use it for disaster recovery?.

   • Create a snapshot of your system by using LV snapshots or RAID splitting. For more information, see Managing logical volume snapshots or Splitting off a RAID image as a separate logical volume. In case of upgrading a virtual machine, you can create a snapshot of the whole VM. You can also manage snapshot and rollback boot entries by using the Boom utility. For more information, see What is BOOM and how to install it? and Managing system upgrades with snapshots.

     Note

     Because LVM snapshots do not create a full backup of your system, you might not be able to recover your system after certain upgrade failures. As a result, it is safer to create a full backup by using the ReaR utility.

2. On your RHEL 9 system, start the upgrade process:

   # leapp upgrade --target <_target_os_version_>

   Replace target_os_version with the target OS version, for example 10.0. If no target OS version is defined, Leapp uses the default target OS version specified in the table 1.1 in Supported upgrade paths.

   • If you are using custom repositories from the /etc/yum.repos.d/ directory for the upgrade, enable the selected repositories as follows:

     # leapp upgrade --enablerepo <repository_id1> --enablerepo <repository_id2> ...

   • If you are upgrading without RHSM or by using RHUI, add the --no-rhsm option.
   • If you are upgrading by using an ISO image, add the --no-rhsm and --iso <file_path> options. Replace <file_path> with the file path to the saved ISO image, for example /home/rhel9.iso.
   • If you have an Extended Upgrade Support (EUS) or Advanced Update Support (AUS) subscription, add the --channel channel option. Replace channel with the value you used with the leapp preupgrade command, for example, eus or aus. Note that you must use the same value with the --channel option in both the leapp preupgrade and leapp upgrade commands.

   • If you are using RHEL for Real Time or the Real Time for Network Functions Virtualization (NFV) in your Red Hat OpenStack Platform, enable the deployment by using the --enablerepo option. For example:

     # leapp upgrade --enablerepo rhel-10-for-x86_64-rt-rpms

     For more information, see Configuring Real-Time Compute.

   • If you are upgrading with LiveMode, set the LEAPP_UNSUPPORTED=1 environment variable and use the --enable-experimental-feature option with the livemode value. For example:

     # LEAPP_UNSUPPORTED=1 leapp upgrade --enable-experimental-feature livemode

     For more information, see Configuring the upgrade from RHEL 9.7 to RHEL 10.1 with LiveMode.

     Important

     LiveMode is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

     For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.

3. At the beginning of the upgrade process, Leapp repeats the pre-upgrade phase described in Reviewing the pre-upgrade report:

   • If the system is upgradable, Leapp downloads necessary data and prepares an RPM transaction for the upgrade.
   • If your system does not meet the parameters for a reliable upgrade, Leapp terminates the upgrade process and provides a record describing the issue and a recommended solution in the /var/log/leapp/leapp-report.txt file. For more information, see Troubleshooting.

4. Manually restart the system:

   # reboot

   The system boots into a RHEL 10-based initial RAM disk image, initramfs. Leapp upgrades all packages and automatically restarts to the RHEL 10 system.

   Alternatively, you can run the leapp upgrade command with the --reboot option and skip this manual step.

   If a failure occurs, investigate logs and known issues as described in Troubleshooting.

5. Log in to the RHEL 10 system and verify its state as described in Verifying the post-upgrade state.
6. Perform all post-upgrade tasks described in the upgrade report and in Performing post-upgrade tasks.

Procedure

1. Ensure that you have a full system backup or a virtual machine snapshot. You can use the following backup options:

   • Create a full backup of your system by using the Relax-and-Recover (ReaR) utility. For more information, see Recovering and restoring a system and What is Relax and Recover (ReaR) and how can I use it for disaster recovery?.

   • Create a snapshot of your system by using LV snapshots or RAID splitting. For more information, see Managing logical volume snapshots or Splitting off a RAID image as a separate logical volume. In case of upgrading a virtual machine, you can create a snapshot of the whole VM. You can also manage snapshot and rollback boot entries by using the Boom utility. For more information, see What is BOOM and how to install it? and Managing system upgrades with snapshots.

     Note

     Because LVM snapshots do not create a full backup of your system, you might not be able to recover your system after certain upgrade failures. As a result, it is safer to create a full backup by using the ReaR utility.

2. On your RHEL 9 system, start the upgrade process:

   # leapp upgrade --target <_target_os_version_>

   Replace target_os_version with the target OS version, for example 10.0. If no target OS version is defined, Leapp uses the default target OS version specified in the table 1.1 in Supported upgrade paths.

   • If you are using custom repositories from the /etc/yum.repos.d/ directory for the upgrade, enable the selected repositories as follows:

     # leapp upgrade --enablerepo <repository_id1> --enablerepo <repository_id2> ...

   • If you are upgrading without RHSM, add the --no-rhsm option.
   • If you are upgrading by using an ISO image, add the --no-rhsm and --iso <file_path> options. Replace <file_path> with the file path to the saved ISO image, for example /home/rhel9.iso.
   • If you have an Extended Upgrade Support (EUS) or Advanced Update Support (AUS) subscription, add the --channel channel option. Replace channel with the value you used with the leapp preupgrade command, for example, eus or aus. Note that you must use the same value with the --channel option in both the leapp preupgrade and leapp upgrade commands.

   • If you are using RHEL for Real Time or the Real Time for Network Functions Virtualization (NFV) in your Red Hat OpenStack Platform, enable the deployment by using the --enablerepo option. For example:

     # leapp upgrade --enablerepo rhel-10-for-x86_64-rt-rpms

     For more information, see Configuring Real-Time Compute.

3. At the beginning of the upgrade process, Leapp repeats the pre-upgrade phase described in Reviewing the pre-upgrade report.

   • If the system is upgradable, Leapp downloads necessary data and prepares an RPM transaction for the upgrade.
   • If your system does not meet the parameters for a reliable upgrade, Leapp terminates the upgrade process and provides a record describing the issue and a recommended solution in the /var/log/leapp/leapp-report.txt file. For more information, see Troubleshooting.

4. Manually restart the system:

   # reboot

   In this phase, the system boots into a RHEL 10-based initial RAM disk image, initramfs. Leapp upgrades all packages and automatically restarts to the RHEL 10 system.

   Alternatively, you can run the leapp upgrade command with the --reboot option and skip this manual step.

   If a failure occurs, investigate logs and known issues as described in Troubleshooting.

5. Log in to the RHEL 10 system and verify its state as described in Verifying the post-upgrade state.
6. Perform all post-upgrade tasks described in the upgrade report and in Performing post-upgrade tasks.