Chapter 4. Reviewing the pre-upgrade report

Procedure

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

   # leapp preupgrade --target <_target_os_version_>

   Copy to Clipboard Toggle word wrap

   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> ...

     Copy to Clipboard Toggle word wrap

     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

     Copy to Clipboard Toggle word wrap

     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.

      Note

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

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

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

Procedure

1. Install the cockpit-leapp plug-in:

   # dnf install cockpit-leapp

   Copy to Clipboard Toggle word wrap
2. Log in to the web console as root or as a user that has permissions to enter administrative commands with sudo.

3. On your RHEL 9 system, perform the pre-upgrade phase either from the command line or from the web console terminal:

   # leapp preupgrade --target <target_os_version>

   Copy to Clipboard Toggle word wrap

   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> ...

     Copy to Clipboard Toggle word wrap
   • 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

     Copy to Clipboard Toggle word wrap

     For more information, see Configuring Real-Time Compute.

4. In the web console, select Upgrade Report from the navigation menu to review all reported problems. Inhibitor problems prevent you from upgrading until you have resolved them. To view a problem in detail, select the row to open the Detail pane.

   Figure 4.1. In-place upgrade report in the web console

   

   View larger image

   

   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.

5. In certain configurations, the Leapp utility generates true or false questions that you must answer manually. If the Upgrade Report contains a Missing required answers in the answer file row, complete the following steps:

   1. Select the Missing required answers in the answer file row to open the Detail pane. The default answer is stated at the end of the remediation command.
   2. To confirm the default answer, select Add to Remediation Plan to start the remediation later or Run Remediation to start the remediation immediately.

   3. To select the non-default answer instead, run the leapp answer command in the terminal, specifying the question you are responding to and your confirmed answer.

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

      Copy to Clipboard Toggle word wrap
      Note

      You can also 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.

6. Some problems have remediation commands that you can run to automatically resolve the problems. You can run remediation commands individually or all together in the remediation command.

   1. To run a single remediation command, open the Detail pane for the problem and click Run Remediation.

   2. To add a remediation command to the remediation plan, open the Detail pane for the problem and click Add to Remediation Plan.

      Figure 4.2. Detail pane

      

      View larger image

      
   3. To run the remediation plan containing all added remediation commands, click the Remediation plan link in the top right corner above the report. Click Execute Remediation Plan to run all listed commands.
7. After reviewing the report and resolving all reported problems, repeat steps 3-7 to rerun the report to verify that you have resolved all critical issues.