Before You Begin

Before you begin the upgrade process:

Read the upgrade prerequisites that are common to both a standard environment and a self-hosted engine environment.
If applicable, read the additional prerequisites for a self-hosted engine environment.
Ensure the engine or self-hosted engine and KVM hosts are updated to the latest version of 4.4 before you begin the upgrade process. See Updating engine or self-hosted engine to latest version of 4.4 and Migrating KVM hosts to the latest version of 4.4.
Don't upgrade the KVM hosts until after the engine or self-hosted engine upgrade is completed.
Upgrade all Oracle Linux 7 KVM hosts to Oracle Linux 8.

(ULN registered hosts only) Run the following commands on the engine and KVM hosts:

echo "Disabling yum module virt:ol"
/usr/bin/dnf -y module disable virt:ol  > /dev/null

echo "Enabling yum module virt:kvm_utils3"
/usr/bin/dnf -y module enable virt:kvm_utils3  > /dev/null

echo "Enabling module pki-deps"
/usr/bin/dnf -y module enable pki-deps  > /dev/null

echo "Enabling module postgresql:13"
/usr/bin/dnf -y module enable postgresql:13  > /dev/null

echo "Enabling module nodejs:18"
/usr/bin/dnf -y module reset nodejs  > /dev/null
/usr/bin/dnf -y module enable nodejs:18  > /dev/null

echo "Exclude ansible-core updates from OL ol8_appstream"
/usr/bin/dnf -y config-manager --save --setopt="exclude=ansible-core"  > /dev/null

echo "Version lock gluster-ansible* packages"
/usr/bin/dnf install -y 'dnf-command(versionlock)' > /dev/null
/usr/bin/dnf versionlock gluster-ansible-cluster-1.0-2.1*  > /dev/null
/usr/bin/dnf versionlock gluster-ansible-features-1.0.5-9*  > /dev/null
/usr/bin/dnf versionlock gluster-ansible-infra-1.0.4-18*  > /dev/null
/usr/bin/dnf versionlock gluster-ansible-maintenance-1.0.1-10*  > /dev/null
/usr/bin/dnf versionlock gluster-ansible-repositories-1.0.1-3*  > /dev/null
/usr/bin/dnf versionlock gluster-ansible-roles-1.0.5-23*  > /dev/null

Prerequisites

Ensure the following prerequisites are met before beginning the upgrade:

The OS for the engine host must be Oracle Linux 8.8 or later (8.x). If it's not, then update the engine host before you upgrade the engine to 4.5.
All data centers and clusters in the environment must have the cluster compatibility level set to version 4.6 or later.
All virtual machines in the environment must have the same compatibility level as their cluster.
If you use an external CA to sign HTTPS certificates, follow the steps in Replacing the Oracle Linux Virtualization Manager Apache SSL Certificate. The backup and restore include the 3rd-party certificate, so you can sign in to the Administration portal after the upgrade. Ensure the CA certificate is added to system-wide trust stores of all clients to ensure the foreign menu of virt-viewer works.
For self-hosted engine environments:
- Make note of the MAC address of the self-hosted engine if you're using DHCP and want to use the same IP address. The deploy script prompts you for this information.
- Set the cluster scheduling policy to cluster_maintenance to prevent automatic virtual machine migration during the upgrade.

Updating engine or self-hosted engine to latest version of 4.4

Before upgrading to 4.5, you must update the engine or self-hosted engine to the latest version of 4.4.

(Self-hosted engine only) Migrate virtual machines and enable global maintenance mode.
- Migrate all other virtual machines off the host that contains the self-hosted engine virtual machine. Move the virtual machines to another host within the same cluster. During the upgrade, the host can only contain the self-hosted engine virtual machine (no other virtual machines can be on the host). Use Live Migration to minimize virtual machine down-time. See Migrating Virtual Machines between Hosts.
- Enable global maintenance mode:
  1. Sign in to the KVM host where the self-hosted engine is running or any KVM host configured to run the self-hosted engine.
  2. Enable global maintenance mode:
```
hosted-engine --set-maintenance --mode=global
```
  3. Confirm that the environment is in global maintenance mode before proceeding:
```
hosted-engine --vm-status
```
  4. You should see the following message:
```
!! Cluster is in GLOBAL MAINTENANCE mode !!
```
On the engine or self-hosted engine machine, update to the latest Oracle Linux Virtualization Manager Release 4.4 package.
```
dnf update oracle-ovirt-release-el8                    
```
Check for updated packages:
```
engine-upgrade-check
```
Update the setup packages:
```
dnf update ovirt\*setup\*
```
Update the engine or self-hosted engine:
```
engine-setup
```
Important:
The update process might take some time. Don't stop the process before it completes.

The engine-setup script:
- Prompts you with some configuration questions
  
  For more information, see Engine Configuration Options in the Oracle Linux Virtualization Manager: Getting Started.
- Stops the ovirt-engine service.
- Downloads and installs the updated packages.
- Backs up and updates the database.
- Performs postinstallation configuration.
- Starts the ovirt-engine service.
Note:
The engine-setup script displays stored configuration values supplied during the initial engine installation process. These stored values display when previewing the configuration and might not be up-to-date if you ran engine-config after installation. However, engine-setup won't overwrite the updated values.
For example, if you ran engine-config to update SANWipeAfterDelete to true after installation, engine-setup outputs Default SAN wipe after delete: False in the configuration preview. However, engine-setup won't apply this value. Instead it keeps the SANWipeAfterDelete=true setting.

After an update is successful, you see:
```
Execution of setup completed successfully
```
If the update fails, the engine-setup command trie to rollback the installation to its previous state. If you encounter a failed update, detailed instructions display explaining how to restore the installation.
Update the base OS and any optional packages installed on the engine:
```
dnf update
```
If any core libraries or services were upgraded, reboot the system to complete the changes. Run the following command to confirm a reboot is required: dnf needs-restarting -r,
Update the KVM hosts.

When you finish updating the engine or self-hosted engine continue to Upgrading the Engine or Self-Hosted Engine.