Procedure 2.1. Updating Red Hat Virtualization Manager

1. On the Red Hat Virtualization Manager machine, check if updated packages are available:

   # engine-upgrade-check

2. • If there are no updates are available, the command will output the text No upgrade:

     # engine-upgrade-check
     VERB: queue package ovirt-engine-setup for update
     VERB: package ovirt-engine-setup queued
     VERB: Building transaction
     VERB: Empty transaction
     VERB: Transaction Summary:
     No upgrade

     Note

     If updates are expected, but not available, ensure that the required repositories are enabled. See Subscribing to the Required Entitlements in the Installation Guide.
   • If updates are available, the command will list the packages to be updated:

     # engine-upgrade-check
     VERB: queue package ovirt-engine-setup for update
     VERB: package ovirt-engine-setup queued
     VERB: Building transaction
     VERB: Transaction built
     VERB: Transaction Summary:
     VERB:     updated    - ovirt-engine-lib-3.3.2-0.50.el6ev.noarch
     VERB:     update     - ovirt-engine-lib-3.4.0-0.13.el6ev.noarch
     VERB:     updated    - ovirt-engine-setup-3.3.2-0.50.el6ev.noarch
     VERB:     update     - ovirt-engine-setup-3.4.0-0.13.el6ev.noarch
     VERB:     install    - ovirt-engine-setup-base-3.4.0-0.13.el6ev.noarch
     VERB:     install    - ovirt-engine-setup-plugin-ovirt-engine-3.4.0-0.13.el6ev.noarch
     VERB:     updated    - ovirt-engine-setup-plugins-3.3.1-1.el6ev.noarch
     VERB:     update     - ovirt-engine-setup-plugins-3.4.0-0.5.el6ev.noarch
     Upgrade available
     
     Upgrade available

3. Update the ovirt-engine-setup package:

   # yum update ovirt-engine-setup

4. Update the Red Hat Virtualization Manager. By running engine-setup, the script will prompt you with some configuration questions like updating the firewall rules, updating PKI certificates, and backing up the Data Warehouse database. The script will then go through the process of stopping the ovirt-engine service, downloading and installing the updated packages, backing up and updating the database, performing post-installation configuration, and starting the ovirt-engine service.

   Note

   The engine-setup script is also used during the Red Hat Virtualization Manager installation process, and it stores the configuration values that were supplied. During an update, the stored values are displayed when previewing the configuration, and may not be up to date if engine-config was used to update configuration after installation. For example, if engine-config was used to update SANWipeAfterDelete to true after installation, engine-setup will output "Default SAN wipe after delete: False" in the configuration preview. However, the updated values will not be overwritten by engine-setup.

   # engine-setup

   Important

   The update process may take some time; allow time for the update process to complete and do not stop the process once initiated.
5. Update the base operating system and any optional packages installed on the Manager:

   # yum update

   Important

   If any kernel packages were updated, reboot the system to complete the update.

Procedure 2.2. Updating Red Hat Enterprise Linux hosts and Red Hat Virtualization Host

1. Click the Hosts tab and select the host to be updated.
   • If the host requires updating, an alert message under Action Items and an icon next to the host's name indicate that a new version is available.
   • If the host does not require updating, no alert message or icon is displayed and no further action is required.
2. Click Installation → Check for Upgrade to open the Upgrade Host confirmation window.
3. Click OK to begin the upgrade check.
4. If you want to upgrade the host, click Installation → Upgrade to open the Upgrade Host confirmation window.
5. Click OK to update the host. The details of the host are updated in the Hosts tab, and the status will transition through these stages:

   • Maintenance
   • Installing
   • Up

Procedure 2.3. Manually Updating Hosts

1. From the Administration Portal, click the Hosts tab and select the host to be updated.
2. Click Maintenance to place the host into maintenance mode.
3. • On a Red Hat Enterprise Linux host, log in to the host machine and run the following command:

     # yum update

   • On a Red Hat Virtualization Host, log in to the Cockpit user interface, click Tools > Terminal, and run the following command:

     # yum update

4. Restart the host to ensure all updates are correctly applied.

Procedure 3.1. Upgrading to Red Hat Virtualization Manager 4.0

1. On Red Hat Enterprise Virtualization Manager 3.6, back up the environment.

   # engine-backup --scope=all --mode=backup --file=backup.bck --log=backuplog.log

2. Copy the backup file to a suitable device.
3. If the ISO storage domain is on the same host as the engine, back up the contents of /var/lib/exports/iso:

   # cd /var/lib/exports/iso
   # tar zcf iso_domain.tar.gz UUID

   The ISO storage backup file will be restored after the upgrade, in Section 3.3, “Migrating the ISO Domain” .
4. Install Red Hat Enterprise Linux 7. See the Red Hat Enterprise Linux Installation Guide for more information.
5. Install Red Hat Virtualization Manager 4.0. See the Red Hat Virtualization Installation Guide.
6. Copy the backup file to the Red Hat Virtualization Manager 4.0 machine and restore it.

   # engine-backup --mode=restore --file=backup.bck --log=restore.log --provision-db --provision-dwh-db --restore-permissions

   Note

   If the backup contained grants for extra database users, this command will create the extra users with random passwords. You must change these passwords manually if the extra users require access to the restored system. See https://access.redhat.com/articles/2686731.

   Note

   Use the --provision-dwh-db option if the backup contains Data Warehouse data.

   Reports have been deprecated in Red Hat Virtualization 4.0 and will not be restored. See BZ#1340810 for more information.
7. Install optional extension packages if they were installed on the Red Hat Enterprise Virtualization Manager 3.6 machine.

   # yum install ovirt-engine-extension-aaa-ldap ovirt-engine-extension-aaa-misc ovirt-engine-extension-logger-log4j

   Note

   The configuration for these package extensions must be manually reapplied because they are not migrated as part of the backup and restore process.
8. Decommission the Red Hat Enterprise Virtualization Manager 3.6 machine if a different machine is used for Red Hat Virtualization Manager 4.0.
9. Run engine-setup to configure the Manager.

   # engine-setup

10. Run ovirt-engine-rename to rename the Manager only if the FQDN differs from the Red Hat Enterprise Virtualization Manager 3.6 machine, and follow the prompts to set the new details.

    # /usr/share/ovirt-engine/setup/bin/ovirt-engine-rename

1. Create an export directory and set its permissions:

   # mkdir -p /var/lib/exports/iso
   # chown -R 36:36 /var/lib/exports/

2. Extract the ISO domain backup to this directory:

   # cd /var/lib/exports/iso
   # tar zxf iso_domain.tar.gz

3. Set the SELinux context for the files in the export directory:

   # chcon -R system_u:object_r:public_content_rw_t:s0 /var/lib/exports/iso/

4. Create /etc/exports.d/ovirt-engine-iso-domain.exports with the following line:

   /var/lib/exports/iso  *(rw)

5. Edit the following lines in /etc/sysconfig/nfs:

   RPCMOUNTDOPTS="-p 892"
   (..snip..)
   STATDARGS="-p 662 -o 2020"
   (..snip..)
   LOCKD_UDPPORT=32769
   LOCKD_UDPPORT=32803
   RPCRQUOTAOPTS="-p 875"
   

6. Enable the nfs service:

   # systemctl enable nfs
   # systemctl start nfs
   

7. Allow services and ports with firewalld:

   # firewall-cmd --add-service={nfs,rpc-bind}
   # firewall-cmd --add-service={nfs,rpc-bind} --permanent
   
   # firewall-cmd --add-port={32769/udp,32803/tcp,662/tcp,662/udp,875/tcp,875/udp,892/tcp,892/udp}
   # firewall-cmd --add-port={32769/udp,32803/tcp,662/tcp,662/udp,875/tcp,875/udp,892/tcp,892/udp} --permanent
   

Procedure 3.2. Upgrading to RHVH While Preserving Local Storage

1. Ensure the RHEV-H host's local storage is in maintenance mode before starting this process:
   1. Open the Data Centers tab.
   2. Click the Storage tab in the details pane and select the storage domain in the results list.
   3. Click Maintenance.
2. Reinstall the Red Hat Virtualization Host, as described in Installing Red Hat Virtualization Host in the Installation Guide.

   Important

   When selecting the device on which to install RHVH from the Installation Destination screen, do not select the device(s) storing the virtual machines. Only select the device where the operating system should be installed.
   If you are using kickstart to install the host, ensure that you preserve the devices containing the virtual machines by adding the following to the kickstart file, replacing device with the relevant device.

   # clearpart --all --drives=device

   For more information on using kickstart, see Kickstart Syntax Reference in the Red Hat Enterprise Linux 7 Installation Guide.
3. On the reinstalled host, create a directory, for example /data in which to recover the previous environment.

   # mkdir /data

4. Mount the previous local storage in the new directory. In our example, /dev/sdX1 is the local storage:

   # mount /dev/sdX1 /data

5. Set the following permissions for the new directory.

   # chown -R 36:36 /data
   # chmod -R 0755 /data

6. Red Hat recommends that you also automatically mount the local storage via /etc/fstab in case the server requires a reboot:

   # blkid | grep -i sdX1
   /dev/sdX1: UUID="a81a6879-3764-48d0-8b21-2898c318ef7c" TYPE="ext4"
   
   # vi /etc/fstab
   UUID="a81a6879-3764-48d0-8b21-2898c318ef7c" /data    ext4    defaults     0       0

7. In the Administration Portal, create a data center and select Local in the Storage Type drop-down menu.
8. Configure a cluster on the new data center. See Creating a New Cluster in the Administration Guide for more information.
9. Add the host to the Manager. See Adding a Host to the Red Hat Virtualization Manager in the Installation Guide for more information.
10. On the host, create a new directory that will be used to create the initial local storage domain. For example:

    # mkdir -p /localfs 
    # chown 36:36 /localfs
    # chmod -R 0755 /localfs

11. In the Administration Portal, open the Storage tab and click New Domain to create a new local storage domain.
    Define localfs as the Name and /localfs as the Path.
12. Once the local storage is Active, select Import Domain and define the domain's details.
    For example, define Data as the Name, Local on Host as the Storage Type and /data as the Path.
13. Click OK to confirm the message that appears informing you that storage domains are already attached to the data center.
14. Activate the new storage domain:
    1. Open the Data Centers tab.
    2. Click the Storage tab in the details pane and select the new Data storage domain in the results list.
    3. Click Activate.
15. Once the new storage domain is Active, import the virtual machines and their disks:
    1. In the Storage tab, select data.
    2. Select the VM Import tab in the details pane, select the virtual machine(s) and click Import. See Importing Virtual Machines from Imported Data Storage Domains in the Administration Guide for more details.
16. Once you have ensured that all virtual machines have been successfully imported and are functioning properly, you can move localfs to maintenance mode.
    1. Click the Storage tab and select localfs from the results list.
    2. Click the Data Center tab in the details pane.
    3. Click Maintenance, then click OK to move the storage domain to maintenance mode.
    4. Click Detach to open the Detach Storage confirmation window.
    5. Click OK.

Procedure 3.3. Adding an Upgraded Host to a Cluster

1. Upgrade a host in the current cluster to a later version. See Section 2.2, “Updating Hosts” for details.
2. Add the later version host to the current cluster:
   1. Click Maintenance to place the later version host in Maintenance mode.
   2. Click Edit.
   3. In the General tab, select the current cluster in the drop-down list.
   4. Click OK.
   5. Click Activate to bring the later version host out of Maintenance mode.

Procedure 3.4. Adding a New Host to a Cluster

1. Create a new host running a later version of Red Hat Virtualization. See Red Hat Enterprise Linux Hosts (4.0) or Red Hat Enterprise Linux Hosts (4.1) in the Installation Guide for details.
2. Add the later version host to the current cluster:
   1. In the Hosts tab, click New.
   2. Select a Datacenter and a Cluster compatible with the later version of Red Hat Virtualization on the drop-down lists.
   3. Enter the Name, Address, and Password of the new host.
   4. Click OK.

Procedure 3.5. Migrating Virtual Machines

1. Check that all virtual machines can migrate automatically:
   1. In the Virtual Machines tab, select a virtual machine.
   2. Click Edit.
   3. Click the Hosts tab and check that Any Host in Cluster is selected.
   4. Check that Migration Mode is set to Allow manual and automatic migration
   5. Click OK.
2. Place the earlier version hosts in Maintenance mode to trigger automatic migration of the virtual machines:
   1. In the Hosts tab, select an earlier version host.
   2. Click Maintenance to place the host in Maintenance mode.
   3. Click OK.
3. Repeat these steps until all the virtual machines are running on the later version hosts.
4. Change the cluster compatibility level to the later version. See Section 4.1, “Changing the Cluster Compatibility Version” for details.
5. Stop and start each migrated virtual machine:
   1. In the Virtual Machines tab, select a virtual machine.
   2. Click Shutdown.
   3. Click Run.

Procedure 4.1. Changing the Cluster Compatibility Version

1. From the Administration Portal, click the Clusters tab.
2. Select the cluster to change from the list displayed.
3. Click Edit.
4. Change the Compatibility Version to the desired value.
5. Click OK to open the Change Cluster Compatibility Version confirmation window.
6. Click OK to confirm.

Procedure 4.2. Changing the Data Center Compatibility Version

1. From the Administration Portal, click the Data Centers tab.
2. Select the data center to change from the list displayed.
3. Click Edit.
4. Change the Compatibility Version to the desired value.
5. Click OK to open the Change Data Center Compatibility Version confirmation window.
6. Click OK to confirm.