9.11. Upgrading the Manager from 4.2 to 4.3
Follow these same steps when upgrading any of the following:
- the Red Hat Virtualization Manager
- a remote machine with the Data Warehouse service
You need to be logged into the machine that you are upgrading.
If the upgrade fails, the
engine-setup command attempts to restore your Red Hat Virtualization Manager installation to its previous state. For this reason, do not remove the previous version’s repositories until after the upgrade is complete. If the upgrade fails, the
engine-setup script explains how to restore your installation.
Enable the Red Hat Virtualization 4.3 repositories:
# subscription-manager repos \ --enable=rhel-7-server-rhv-4.3-manager-rpms \ --enable=jb-eap-7.2-for-rhel-7-server-rpms
All other repositories remain the same across Red Hat Virtualization releases.
Update the setup packages:
# yum update ovirt\*setup\* rh\*vm-setup-plugins
engine-setupand follow the prompts to upgrade the Red Hat Virtualization Manager, the remote database or remote service:
During the upgrade process for the Manager, the
engine-setupscript might prompt you to disconnect the remote Data Warehouse database. You must disconnect it to continue the setup.
When the script completes successfully, the following message appears:
Execution of setup completed successfully
Disable the Red Hat Virtualization 4.2 repositories to ensure the system does not use any 4.2 packages:
# subscription-manager repos \ --disable=rhel-7-server-rhv-4.2-manager-rpms \ --disable=jb-eap-7-for-rhel-7-server-rpms
Update the base operating system:
# yum updateImportant
If any kernel packages were updated, reboot the machine to complete the upgrade.
The Manager is now upgraded to version 4.3.
9.11.1. Completing the remote Data Warehouse database upgrade
Complete these additional steps when upgrading a remote Data Warehouse database from PostgreSQL 9.5 to 10.
ovirt-engine-dwhdservice is now running on the Manager machine. If the
ovirt-engine-dwhdservice is on a remote machine, stop and disable the
ovirt-engine-dwhdservice on the Manager machine, and remove the configuration files that
# systemctl stop ovirt-engine-dwhd # systemctl disable ovirt-engine-dwhd # rm -f /etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/*
Repeat the steps in Section 9.11, “Upgrading the Manager from 4.2 to 4.3” on the machine hosting the
You can now change the cluster compatibility version to 4.3.