6.4. Upgrading the Manager from 4.1 to 4.2
Upgrade the Red Hat Virtualization Manager from 4.1 to 4.2.
If the upgrade fails, the
engine-setup command attempts to roll your Red Hat Virtualization Manager installation back to its previous state. For this reason, the previous version’s repositories must not be removed until after the upgrade is complete. If the upgrade fails, detailed instructions display that explain how to restore your installation.
- Log in to the Manager machine.
Enable the Red Hat Virtualization 4.2 repositories:
# subscription-manager repos \ --enable=rhel-7-server-rhv-4.2-manager-rpms \ --enable=rhel-7-server-rhv-4-manager-tools-rpms \ --enable=jb-eap-7-for-rhel-7-server-rpms \ --enable=rhel-7-server-ansible-2.9-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:
If you changed the default trust keystore password, you might get a keystore certificate error. If so, update the configuration to reflect the correct password. For more information, see RHV 4.2 - Failed to import provider certificate into the external provider keystore
Disable the Red Hat Virtualization 4.1 repositories to ensure the system does not use any 4.1 packages:
# subscription-manager repos \ --disable=rhel-7-server-rhv-4.1-rpms \ --disable=rhel-7-server-rhv-4.1-manager-rpms \ --disable=rhel-7-server-rhv-4-tools-rpms \ --disable=jb-eap-7.0-for-rhel-7-server-rpms \ --disable=jb-eap-7.1-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.
You must now update the hosts before you can update the cluster and data center compatibility versions.