4.2. Assessing upgradability of RHEL 9 to RHEL 10 from the command line

Procedure

1. On your RHEL 9 system, perform the pre-upgrade phase:

   # leapp preupgrade --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 preupgrade --enablerepo <repository_id1> --enablerepo <repository_id2> ...

     Replace repository_id with the repository IDs.

   • If you are upgrading without RHSM or by using RHUI, add the --no-rhsm option.
   • If you have an Extended Upgrade Support (EUS) or Advanced Update Support (AUS) subscription, add the --channel <channel> option. Replace <channel> with the channel name, for example, eus or aus.

   • 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 preupgrade --enablerepo rhel-10-for-x86_64-rt-rpms

     For more information, see Configuring Real-Time Compute.

2. Examine the report in the /var/log/leapp/leapp-report.txt file and manually resolve all the reported problems. Some reported problems contain remediation suggestions. Inhibitor problems prevent you from upgrading until you have resolved them.

   The report contains the following risk factor levels:

   • High - Very likely to result in a deteriorated system state.
   • Medium - Can impact both the system and applications.
   • Low - Should not impact the system but can have an impact on applications.
   • Info - Informational with no expected impact to the system or applications.

3. In certain system configurations, the Leapp utility generates true or false questions that you must answer manually. If the pre-upgrade report contains a Missing required answers in the answer file message, complete the following steps:

   1. Open the /var/log/leapp/answerfile file and review the true or false questions.

   2. Manually edit the /var/log/leapp/answerfile file, uncomment the confirm line of the file by deleting the # symbol, and confirm your answer as True or False. For more information, see the Troubleshooting tips.

      참고

      Alternatively, you can answer the true or false question by running the following command:

      # leapp answer --section <question_section>.<field_name>=<answer>

4. Repeat the previous steps to rerun the pre-upgrade report to verify that you have resolved all critical issues.