6 Updating Your Environment

You can update your engine, self-hosted engine, and KVM hosts within versions, such as from 4.5 to the latest version of 4.5.

However, if you want to move from one version to another, such as 4.4 to 4.5, this is considered an upgrade. See Upgrading Your Environment to 4.5.

Important:

• (ULN registered hosts only) Before you begin the update process, run the following commands on your 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

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