Red Hat SummitChapter 4. Preparing the RHEL 7 system for an upgrade to RHEL 8
To prepare your RHEL 7 system for the upgrade to RHEL 8, follow these steps before proceeding with the upgrade:
Migrate the GRUB Legacy boot loader to GRUB
After the upgrade, RHEL 7 still uses the GRUB Legacy boot loader. However, GRUB Legacy is not supported on RHEL 7 and later versions. Therefore, you must manually migrate the boot loader to GRUB. For details, see the Upgrading from GRUB Legacy to GRUB section in the
RHEL 7 System Administrator’s Guide.- Resolve potential problems with installed packages. For details, see Section 7.1, “Ensuring that installed packages match the current major RHEL version”.
Adjust custom
System VandUpstartscripts tosystemdservices.On a RHEL 7 system,
systemdreplacesUpstartas the init system. To use the featuressystemdprovides, such as parallel startup of system services at boot time, manually convert legacySystem VandUpstartscripts tosystemdservices. For details, see Converting traditional sysV init scripts to Red Hat Enterprise Linux 7 systemd unit files.Update paths to system directories in your scripts.
On a RHEL 7 system, the
/bin,/sbin,/lib, and/lib64directories have been replaced by symbolic links to their corresponding directory in/usr. For example, on RHEL 8,/binis a symbolic link to the/usr/bin/directory.If you use scripts or applications that expect
/bin,/sbin,/lib, and/lib64to be real directories, adjust them accordingly. For example, you can update the scripts and applications to:-
Use the paths in
/usr, such as/usr/bin/ -
Accept that
/bin,/sbin,/lib, and/lib64are symbolic links instead of directories
-
Use the paths in
Update your YUM scripts and plug-ins to use the YUM 4 API.
RHEL 8 no longer supports the Python API of YUM 3. If you use any scripts or YUM plug-ins that use the legacy API, migrate them to the YUM 4 API. For more information, see Notable changes to the YUM stack.
-
If you miss certain packages after the upgrade, see the Section 7.3, “Installing missing packages after upgrading to RHEL 7” section in the
Troubleshootingchapter. - Review the Considerations in adopting RHEL 8 document and make additional changes to your system if needed.
Update your system to the latest RHEL 7.9 version and reboot the host:
# yum update # reboot- Ensure that all your applications and services are configured and work as expected. For example, if you run a DNS server on the host, verify that the configuration is still valid after the upgrade and that the service works in the same way as it did before the upgrade.
-
Follow the preparation steps described in the Preparing for the upgrade chapter in the
Upgrading from RHEL 7 to RHEL 8document.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}