Chapter 2. Preparing a RHEL 7 system for the upgrade
This procedure describes the steps that are necessary before performing an in-place upgrade to RHEL 8 using the
If you do not plan to use Red Hat Subscription Manager during the upgrade process, follow instructions in Upgrading to RHEL 8 without Red Hat Subscription Manager.
- The system meets conditions listed in Chapter 1, Planning an upgrade.
Ensure your system has been successfully registered to the Red Hat Content Delivery Network (CDN) or Red Hat Satellite 6.5 or later using the Red Hat Subscription Manager.Important
If your system is registered to Satellite Server, ensure that Satellite meets the following conditions:
- Satellite has a subscription manifest with RHEL 8 repositories imported. For more information, see the Managing Subscriptions chapter in the Content Management Guide for the particular version of Red Hat Satellite, for example, for version 6.7.
The following repositories are enabled and synchronized with the latest updates, and published on Satellite:
- Red Hat Enterprise Linux 7 Server RPMs x86_64 7 or Red Hat Enterprise Linux 7 Server RPMs x86_64 7.8
- Red Hat Enterprise Linux 7 Server - Extras (RPMs)
- Red Hat Enterprise Linux 8 for x86_64 - AppStream RPMs x86_64 8.2
Red Hat Enterprise Linux 8 for x86_64 - BaseOS RPMs x86_64 8.2
Verify that you have the Red Hat Enterprise Linux Server subscription attached:
# subscription-manager list --installed +-------------------------------------------+ Installed Product Status +-------------------------------------------+ Product Name: Red Hat Enterprise Linux Server Product ID: 69 Version: 7.8 Arch: x86_64 Status: Subscribed
Ensure you have appropriate repositories enabled. The following commands list repositories for the 64-bit Intel architecture; for other architectures, see Appendix A, RHEL 7 repositories.
Enable the Base repository:
# subscription-manager repos --enable rhel-7-server-rpms
Enable the Extras repository where
Leappand its dependencies are available:
# subscription-manager repos --enable rhel-7-server-extras-rpms
Set the Red Hat Subscription Manager to consume the latest RHEL 7 content:
# subscription-manager release --unset
- Optional: If you want to use custom repositories, configure them per instructions in Configuring custom repositories.
If you use the
yum-plugin-versionlockplug-in to lock packages to a specific version, clear the lock by running:
# yum versionlock clear
See How to restrict yum to install or upgrade a package to a fixed specific package version? for more information.
Ensure you have the system locale set to
$ cat /etc/locale.conf
If the locale is different, follow instructions in How to change system locale on RHEL7?.
Update all packages to the latest RHEL 7 version:
# yum update
Reboot the system:
# yum install leapp leapp-repository
Note that currently you need version 0.10.0-2 or later of both the
Download additional required data files (RPM package changes and RPM repository mapping) attached to the Knowledgebase article Data required by the Leapp utility for an in-place upgrade from RHEL 7 to RHEL 8 and place them in the
/etc/leapp/files/directory. This is necessary for a successful upgrade. Note that currently you need data files from the
leapp-data8.tar.gzarchive or later.
If GRUB is installed outside of the default location, which is
/boot, export the respective environment variable as follows:
# export LEAPP_GRUB_DEVICE="/path_to_device"
- Ensure you have any configuration management (such as Salt, Chef, Puppet, Ansible) disabled or adequately reconfigured to not attempt to restore the original RHEL 7 system.
Ensure your system does not use more than one Network Interface Card (NIC) with a name based on the prefix used by the kernel (
eth). For instructions on how to migrate to another naming scheme before an in-place upgrade to RHEL 8, see How to perform an in-place upgrade to RHEL 8 when using kernel NIC names on RHEL 7.
- Ensure you have a full system backup or a virtual machine snapshot. You should be able to get your system to the pre-upgrade state if you follow standard disaster recovery procedures within your environment. For example, you can use the Relax-and-Recover (ReaR) utility. For more information, see the ReaR documentation and What is Relax and Recover (ReaR) and how can I use it for disaster recovery?. Alternatively, you can use LVM snapshots, or RAID splitting. In case of upgrading a virtual machine, you can create a snapshot of the whole VM.