5.3. Upgrading a RHEL-Based Self-Hosted Engine Environment
A Red Hat Enterprise Virtualization 3.6 self-hosted engine environment can be upgraded to Red Hat Virtualization 4.0. An upgrade utility that is provided with Red Hat Virtualization 4.0 will install Red Hat Enterprise Linux 7 on the Manager virtual machine and restore a backup of the 3.6 Manager database on the new Manager. After the Manager is upgraded to 4.0 you can update the self-hosted engine nodes, and any standard hosts, to 4.0.
Important
The upgrade utility builds a new Manager based on a template. Manual changes or custom configuration to the original Manager such as custom users, SSH keys, and monitoring will need to be reapplied manually on the new Manager.
Note
An in-place upgrade of the Manager virtual machine to Red Hat Enterprise Linux 7 is not supported.
Important
The following procedure is only for upgrading a Red Hat Enterprise Virtualization 3.6 self-hosted engine environment running on Red Hat Enterprise Linux 7 hosts. All data centers and clusters in the environment must have the cluster compatibility level set to version 3.6 before attempting the procedure.
Note
The upgrade must occur on the host that is currently running the Manager virtual machine and is set as the SPM server. The upgrade utility will check for this.
The upgrade process involves the following key steps:
- Place the high-availability agents that manage the Manager virtual machine into the global maintenance mode.
- Enable the required repositories on the host and update the ovirt-hosted-engine-setup and rhevm-appliance packages.
- Run
hosted-engine --upgrade-applianceto upgrade the Manager virtual machine. During the upgrade you will be asked to create a backup of the 3.6 Manager and copy it to the host machine where the upgrade is being performed. - Update the hosts.
- After the Manager virtual machine and all hosts in the cluster have been updated, change the cluster compatibility version to 4.0.
The backup created during the upgrade procedure is not automatically deleted. You need to manually delete it after confirming the upgrade has been successful. The backup disks are labeled with
hosted-engine-backup-*.
Prerequisites
- The
/var/tmpdirectory must have at least 5 GB of free space to extract the appliance files. If it does not, you can specify a different directory or mount alternate storage that does have the required space. The VDSM user and KVM group must have read, write, and execute permissions on the directory. - The self-hosted engine storage domain must have additional free space for the new appliance being deployed (50 GB by default). To increase the storage on iSCSI or Fibre Channel storage, you must manually extend the LUN size on the storage and then extend the storage domain using the Manager. See Increasing iSCSI or FCP Storage in the Administration Guide for more information about resizing a LUN.
Procedure 5.4. Upgrading the Self-Hosted Engine
- Disable the high-availability agents on all the self-hosted engine nodes. To do this run the following command on any host in the cluster.
# hosted-engine --set-maintenance --mode=global
Note
Runhosted-engine --vm-statusto confirm that the environment is in maintenance mode. - On the host that is currently set as SPM and contains the Manager virtual machine, enable the required repository.
# subscription-manager repos --enable=rhel-7-server-rhv-4-mgmt-agent-rpms
- Migrate all virtual machines except the Manager virtual machine to alternate hosts.
- On the host, update the Manager virtual machine packages.
# yum update ovirt-hosted-engine-setup rhevm-appliance
If the rhevm-appliance package is missing, install it manually before updating ovirt-hosted-engine-setup.# yum install rhevm-appliance
# yum update ovirt-hosted-engine-setup
- Run the upgrade utility to upgrade the Manager virtual machine. If not already installed, install the screen package, which is available in the standard Red Hat Enterprise Linux repository.
# yum install screen
# screen
# hosted-engine --upgrade-appliance
Note
You will be prompted to select the appliance if more than one is detected, and to create a backup of the Manager database and provide its full location. - After the upgrade is complete, disable global maintenance:
# hosted-engine --set-maintenance --mode=none
If anything went wrong during the upgrade, power off the Manager by using the
hosted-engine --vm-poweroff command, then rollback the upgrade by running hosted-engine --rollback-upgrade.
To upgrade the hosts in the self-hosted engine environment, see Section 5.5, “Upgrading Hosts in a Self-Hosted Engine Environment”.
