Skip to content

OSVDC Series: oVirt 3.6 Cluster Upgrade

Richard Harmonson edited this page Aug 17, 2019 · 25 revisions

OSVDC: oVirt 3.6 Cluster Upgrade


Revised: August 17, 2019; Provided new document describing updates between minor releases

Revised: 2018; Refer readers to Ovirt Release notes for cluster upgrade.

Revised: July 29, 2017; Updated oVirt Documentation is much improved and more complete then mine. See links below.

Revised: October 20, 2016; correction yum update "ovirt-engine-setup*"

Published: July 1, 2016



This information is depreciated. Since authoring this article, the oVirt project has provided a new 'updates between minor releases' that is well written. <-- I used this one last upgrade and it was easy to follow and painless.

https://ovirt.org/documentation/upgrade-guide/chap-Updates_between_Minor_Releases.html

The earlier instructions given at the URL below do have merit and I would advise reviewing them as well.

https://ovirt.org/documentation/self-hosted/chap-upgrading_the_self-hosted_engine.html


Engine

SSH to either oVirt Host. Assumption is oVirt Engine Appliance is up and running with all VMs powered off. The last is not a requirement per se.

# hosted-engine --set-maintenance --mode=global

SSH to oVirt Engine Appliance.

# yum update "ovirt-engine-setup*"
# engine-setup

Hosts

Connect to oVirt Engine Web Administration web portal. Note the Hosted Engine current Host, e.g. hosted_engine_1. Update that host last.

Place hosted_engine_2 in maintenance mode using the portal.

SSH to hosted_engine_2.

# yum -y update
# restart

After reboot, verify hosted_engine_2's operation using hosted-engine --vm-status to verify its score is 3400. Using the portal, it will continue to show a upgrade is available for the host. Selecting upgrade after "yum -y update" will (now) complete successfully. If so, move to the next Host and repeat the same steps.

For the last host, hosted-engine_1, place it in maintenance mode and use hosted-engine --vm-status to monitor the oVirt Engine Appliance migration to another Host. Alternatively, use the portal to both migrate the appliance then set the Host in maintenance mode.


Note

In my installation, hosted_engine_1 was the initial Host and where I installed the appliance package. As such, the yum upgrade task takes significantly longer with the download of the appliance package. You may want to exclude if you bandwidth is limited. Untested but updating the RPM should only be necessary to redeploying a fresh installation of the Engine.


As with the hosted_engine_2, execute yum, restart, and monitor until a score of 3400 is reported. Execute the following to complete the upgrade.

# hosted-engine --set-maintenance --mode=none

Done!?

Yes. This assumes you are upgrading within the same minor version, e.g. 3.6.1 to 3.6.2 versus 3.5 to 3.6. Otherwise, select the Cluster within the oVirt Manager portal, edit, and update "Capability Version" to the new release to benefit from its new features.

Next

Next article in the series is Root Certificate Authority (PKI) with Dogtag 10.3 on Fedora 24.

Clone this wiki locally