Red Hat Summit Red Hat SummitSupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

Chapter 2. Planning an upgrade to RHEL 10

In-place upgrades allow you to upgrade to the latest version of RHEL without losing existing configurations and system subscriptions. In general, in-place upgrades are less time-consuming and costly than a fresh install of RHEL. However, not all systems are eligible for an in-place upgrade. Before beginning your upgrade from RHEL 9 to RHEL 10, review system requirements, limitations, and other considerations.

2.1. Planning an upgrade from RHEL 9 to RHEL 10
Link kopieren

An in-place upgrade is the recommended and supported method for upgrading your system to the next major version of RHEL.

Consider the following before upgrading to RHEL 10:

  • Applications - You can migrate applications installed on your system by using the Leapp utility. However, in certain cases, you have to create custom actors, which specify actions to be performed by Leapp during the upgrade, for example, reconfiguring an application or installing a specific hardware driver. For more information, see Handling the migration of your custom and third-party applications. Note that custom actors are unsupported by Red Hat.

    Important

    The SHA-1 algorithm has been deprecated in RHEL 9. If your system contains any packages with RSA/SHA-1 signatures, the upgrade is inhibited. Before upgrading, either remove these packages or contact the vendor for packages with RSA/SHA-256 signatures. For more information, see SHA-1 deprecation in Red Hat Enterprise Linux 9.

  • Boot loader - You cannot switch the boot loader from BIOS to UEFI on RHEL 9 or RHEL 10. If your RHEL 9 system uses BIOS and you want your RHEL 10 system to use UEFI, perform a fresh install of RHEL 9 instead of an in-place upgrade. For more information, see Is it possible to switch the BIOS boot to UEFI boot on preinstalled Red Hat Enterprise Linux machine?
  • Customization - To use custom repositories, see the Configuring custom repositories Knowledgebase article.
  • Downtime - The upgrade process can take from several minutes to several hours.
  • High Availability - If you are using the High Availability add-on, follow the Recommended Practices for Applying Software Updates to a RHEL High Availability or Resilient Storage Cluster Knowledgebase article.
  • Language - All Leapp reports, logs, and other generated documentation are in English, regardless of the language configuration.

  • Operating system - The operating system is upgradable by the Leapp utility under the following conditions:

    • The source OS version is installed on a system with one of the following supported architectures:

      • 64-bit Intel, AMD, and ARM

        Important

        For the 64-bit ARM architecture, in-place upgrades are supported only on systems running the 4k page size kernel. The Leapp utility does not support in-place upgrades if the system is booted with the 64k page size kernel.

      • IBM POWER (little endian)

      • 64-bit IBM Z

        For more information, see Red Hat certified hardware.

    • Minimum hardware requirements for RHEL 10 are met.
    • You have access to up-to-date content for the selected source and target OS versions. See Preparing a RHEL 9 system for the upgrade for more information.

  • Public clouds

    • Pay-As-You-Go

      • RHUI - The in-place upgrade is supported for on-demand Pay-As-You-Go (PAYG) instances that use Red Hat Update Infrastructure (RHUI) on Amazon Web Services (AWS) on all supported architectures, and on Microsoft Azure and Google Cloud only on the Intel architecture. For all supported clouds and architectures with PAYG using RHUI but not SAP HANA, only the latest upgrade path is supported.

      • CDN - The in-place upgrade is supported for on-demand Pay-As-You-Go (PAYG) instances that use Red Hat Content Delivery Network (CDN).

        Note

        You can verify that your RHEL cloud instance consumes RHEL content from CDN by confirming that you have the redhat-cloud-client-configuration-cdn package installed. If it is not installed, then you are consuming the content from RHUI.

    • Bring Your Own Subscription - The in-place upgrade is supported for Bring Your Own Subscription instances on all public clouds that use RHSM for a RHEL subscription.
  • Real Time for Network Functions Virtualization (NFV) in Red Hat OpenStack Platform - Upgrades on real-time systems are supported.
  • RHEL for Real Time - Upgrades on real-time systems are supported.
  • SAP HANA - Upgrades with SAP HANA are currently unsupported.

  • Satellite

  • Security - Evaluate this aspect before the upgrade and take additional steps when the upgrade process completes. Consider especially the following:

    • Before the upgrade, define the security standard your system has to comply with and understand the security changes in RHEL 10.
    • During the upgrade process, the Leapp utility sets SELinux mode to permissive.
    • Leapp supports in-place upgrades of RHEL 9.6 and later systems in Federal Information Processing Standard (FIPS) 140 mode to RHEL 10 FIPS-mode-enabled systems. FIPS mode stays enabled throughout the complete upgrade process.
    • After the upgrade is finished, re-evaluate and re-apply your security policies. For information about applying and updating security policies, see Applying security policies.

  • Storage and file systems

Notable known limitations of the Leapp utility include:

  • Known limitations - Notable known limitations of Leapp currently include:

    • Network based multipath and network storage that use Ethernet or Infiniband are not supported for the upgrade. This includes SAN using FCoE and booting from SAN using FC. Note that SAN using FC is supported.
    • The in-place upgrade is not supported for systems with Ansible Automation Platform installed. To use a RHEL 9 Ansible Automation Platform installation on RHEL 10, see the Red Hat Knowledgebase solution How do I migrate my Ansible Automation Platform installation from one environment to another?.
    • Red Hat JBoss Enterprise Application Platform (EAP) is not supported for the upgrade to RHEL 10. You must manually install and configure JBoss EAP on your system after the upgrade.
    • The Stratis filesystem is not supported for the upgrade.

You can use Red Hat Lightspeed to determine which of the systems you have registered to Red Hat Lightspeed is on a supported upgrade path to RHEL 10. Note that the Advisor recommendation considers only the RHEL 9 minor version and does not perform a pre-upgrade assessment of the system. See also Advisor-service recommendations overview.

Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Theme

© 2026 Red HatNach oben