5 Upgrading Your Environment to 4.5

You can upgrade Oracle Linux Virtualization Manager environment from the latest version of 4.4 to 4.5 by upgrading the engine or self-hosted engine and KVM hosts.

WARNING:

Upgrading from 4.4 to 4.5 with Gluster 8 storage in the environment is supported for Oracle 8 KVM hosts, but isn't supported for Oracle 9 KVM hosts.

Important:

Before you upgrade, be aware of the following preprequisites.

• The engine, self-hosted engine, and KVM hosts must be updated to the latest version of 4.4. See Updating engine or self-hosted engine to latest version of 4.4 and Updating KVM hosts to the latest version of 4.4.
• All Oracle Linux 7 KVM hosts must be upgraded to Oracle Linux 8 before you upgrade the environment to 4.5.
• Upgrading from 4.3 to 4.5 isn't supported. You must first upgrade to the latest version of 4.4. For more information, see the Oracle Linux Virtualization Manager 4.4: Administration Guide.
• If you use a local yum mirror configuration, you must redo the yum mirror configuration in the engine and hosts after updating the ovirt-release package and before running the update.

Important:

(ULN registered hosts only) Before you begin the update process, 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 --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

Considerations

• Plan for any necessary virtual machine downtime. After you update the clusters' compatibility versions, a new hardware configuration is automatically applied to each virtual machine after it reboots. You must reboot any running or suspended virtual machines as soon as possible to apply the configuration changes.

• Ensure the environment meets the requirements for 4.5. See Requirements and Scalability Limits in the Oracle Linux Virtualization Manager: Architecture and Planning Guide.

• Clusters must have a minimum of two (2) KVM hosts (in the same cluster) to perform a live migration of virtual machines when you are upgrading the specific KVM host that's in Maintenance mode.

Note:

Connected hosts and virtual machines can continue to work while you upgrade the engine.