The preupgrade phase checks whether the system is fully ready for the upgrade.

After you have completed the /var/log/leapp/answerfile and verified that /var/log/leapp/leapp-report.txt no longer reports risks, upgrade the system as follows:

1. Using a console, connect to the system or the Oracle Cloud Infrastructure instance that you're upgrading.

   • If you're upgrading a remote system configured with a VNC server, connect to the system by using a VNC client.

   • If you're working on an Oracle Cloud Infrastructure instance, connect to the instance through the console connection you previously created in Preparing for the Upgrade. For instructions, see Connecting to the Serial Console in https://docs.oracle.com/iaas/Content/Compute/References/serialconsole.htm#Instance_Console_Connections .

     For example, on a local terminal window, the command that's provided to connect to the instance might resemble the following syntax:

     ssh -o ProxyCommand='ssh additional-commands

     If the command doesn't work at first use, you might need to specify the -i path-to-key option, for example:

     ssh -i path-to-key -o ProxyCommand='ssh -i path-to-key additional-commands

     Because OCI requests only rsa keys, on some systems, you might need to add the following in the /etc/ssh/ssh_config directory:

     HostkeyAlgorithms +ssh-rsa
     PubkeyAcceptedAlgorithms +ssh-rsa 

2. On a separate terminal window of the system or instance to be upgraded, run the upgrade command with the appropriate command argument, depending on whether you're upgrading a system or an Oracle Cloud Infrastructure instance.

   • On a system:

     sudo leapp upgrade --oraclelinux [--enablerepo repository]

   • On an instance in Oracle Cloud Infrastructure:

     sudo leapp upgrade --oci [--enablerepo repository]

   For detailed information about the command arguments, see Using Command Arguments to Enable Repositories.

3. Verify that the report summary returns no errors or inhibitors. For example, the following report shows no errors or inhibitors:

   Debug output written to /var/log/leapp/leapp-upgrade.log
   
   =========================================== 
                REPORT OVERVIEW
   ===========================================
   HIGH and MEDIUM severity reports:
       1. Packages not signed by Oracle found on the system
       2. Difference in Python versions and support in OL 8
       3. Default Boot Kernel
       4. Module pam_pkcs11 will be removed from PAM configuration
       5. Oracle Autonomous Linux managed instance upgrade requires user to accept specific package update requirements for Oracle Autonomous Linux
       6. Oracle Autonomous Linux managed instance upgrade requires user to accept certain software sources requirements.
   
   Reports summary:
       Errors: 0
       Inhibitors: 0
       HIGH severity reports: 2
       MEDIUM severity reports: 4
       LOW severity reports: 1
       INFO severity reports: 2
   
   Before continuing consult the full report:
       A report has been generated at /var/log/leapp/leapp-report.json
       A report has been generated at /var/log/leapp/leapp-report.txt
   
   =========================================== 
              END OF REPORT OVERVIEW
   =========================================== 

   If any errors or inhibitors appear, resolve them before rebooting the system.

4. Reboot the system.

   sudo reboot

5. While the system reboots, monitor the progress on the console.

   At the completion of the boot process, the utility automatically proceeds with upgrading packages. This operation takes awhile to complete and also includes multiple automatic reboots.

   Caution:

   Do not interrupt the ongoing processes at this stage. Wait until the login screen appears, which indicates that the entire upgrade process has completed. Only then can you begin to use the system.

6. When the login screen appears on the console, log in with the proper credentials.

After the completion of an instance upgrade, the instance retains its Oracle Linux 7 base image on the Instance Details page of the Oracle Cloud Infrastructure console, for example, Oracle-Linux-7.9-2020-11.10-1. You can apply a custom tag so you can track the upgrades that have been performed on the instance after its creation.

Upon completion, the upgrade process generates the same files as the preupgrade phase: a process log, a report, and the /var/log/leapp/answerfile. On a terminal, perform the following steps:

1. Examine the /var/log/leapp/leapp-report.txt and fulfill any important recommendations to be completed after the upgrade process.

2. Perform the following verifications:

   To verify the system's new OS version, type:

   cat /etc/oracle-release

   To check the system's kernel version, type this command to verify that the kernel contains the el8 substring:

   uname -r

   You can also identify the system's default kernel with the following command:

   sudo grubby --default-kernel