Red Hat Training
A Red Hat training course is available for Red Hat Virtualization
Chapter 2. Upgrading from 3.6 to Red Hat Virtualization 4.2
You cannot upgrade the Manager directly from 3.6 to 4.2. You must upgrade your environment in the following sequence:
- Update the 3.6 Manager to the latest version of 3.6
- Upgrade the Manager from 3.6 to 4.0
- Upgrade the Manager from 4.0 to 4.1
- Upgrade the Manager from 4.1 to 4.2
If you are upgrading RHEV-H hosts that use local storage, see Appendix C, Upgrading from RHEV-H 3.6 to RHVH 4.2 While Preserving Local Storage.
- Update the compatibility version of the clusters
- Update the compatibility version of the data centers
- If you backed up an ISO storage domain that was hosted on the 3.6 Manager, restore the ISO domain in the upgraded environment
- Replace SHA-1 certificates with SHA-256 certificates
2.1. Updating the Red Hat Virtualization Manager
Updates to the Red Hat Virtualization Manager are released through the Content Delivery Network.
On the Red Hat Virtualization Manager machine, check if updated packages are available:
Update the setup packages:
# yum update rhevm-setup
Update the Red Hat Virtualization Manager. 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 Red Hat Virtualization Manager 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
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 Manager:
# yum updateImportant
If any kernel packages were updated, reboot the host to complete the update.