Chapter 9: Updates Between Minor Releases
To upgrade from your current version of 4.3 to the latest version, for example, from 4.3.7 to 4.3.8, update the Engine and then update the hosts.
Update the oVirt Engine
Updates to the oVirt Engine are released through the oVirt repositories.
On the oVirt Engine machine, check if updated packages are available:
Note: If updates are expected, but not available, enable the required repositories installing https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm
Update the setup packages:
# yum update ovirt*setup*
Update the oVirt Engine. The
engine-setupscript prompts you with some configuration questions, then stops the ovirt-engine service, downloads and installs the updated packages, backs up and updates the database, performs post-installation configuration, and starts the ovirt-engine service.
engine-setupscript is also used during the oVirt Engine installation process, and it stores the configuration values supplied. During an update, the stored values are displayed when previewing the configuration, and may not be up to date if
engine-configwas used to update configuration after installation. For example, if
engine-configwas used to update
engine-setupwill output “Default SAN wipe after delete: False” in the configuration preview. However, the updated values will not be overwritten by
Important: The update process may take some time; allow time for the update process to complete and do not stop the process once initiated.
Update the base operating system and any optional packages installed on the Engine:
# yum update
Important: If the update upgraded any kernel packages, reboot the system to complete the changes.
Update the Hosts
Use the host upgrade manager to update individual hosts directly from the oVirt Engine.
Note: The upgrade manager only checks host with a status of
Non-operational, but not
Important: On oVirt Node 4.0+, the update only preserves modified content in the /etc and /var directories. Modified data in other paths is overwritten during an update.
If migration is enabled at the cluster level, virtual machines are automatically migrated to another host in the cluster. Update a host when its usage is relatively low.
Ensure that the cluster contains more than one host before performing an update. Do not update all hosts at the same time, as one host must remain available to perform Storage Pool Manager (SPM) tasks.
Ensure that the cluster to which the host belongs has sufficient memory reserve for its hosts to perform maintenance. Otherwise, the virtual machine migration operation will hang and fail. You can reduce the memory usage of this operation by shutting down some or all virtual machines before updating the host.
You cannot migrate a virtual machine using a vGPU to a different host. Virtual machines with vGPUs installed must be shut down before updating the host.
- Ensure the correct repositories are enabled. You can check which repositories are currently enabled by running yum repolist.
For oVirt Nodes the ovirt-release43 rpm is already installed
For Enterprise Linux hosts:
# yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm
Click Compute → Hosts and select the host to be updated.
Click Installation → Check for Upgrade.
Click OK to begin the upgrade check.
Click Installation → Upgrade.
Click OK to update the host. The details of the host are updated in Compute → Hosts and the status will transition through these stages:
After the update, the host is rebooted. Once successfully updated, the host displays a status of
Up. If any virtual machines were migrated off the host, they are now migrated back.
Note: If the update fails, the host’s status changes to Install Failed. From Install Failed you can click Installation → Upgrade again.
Repeat this procedure for each host in the oVirt environment.
The oVirt Project recommends updating the hosts from the Engine; however, you can also update the hosts using
yum update. See Appendix C: Manually Updating Hosts for more information.
Prev: Chapter 8: Post-Upgrade Tasks
Next: Appendix A: Updating an Offline oVirt Engine
Adapted from RHV 4.2 documentation - CC-BY-SA