Chapter 4 Upgrade Path

You can upgrade Oracle Linux Virtualization Manager from Release 4.2.8 to Release 4.3.6 by upgrading your engine and KVM hosts.

4.1 Upgrading the Engine

To upgrade your engine install the ovirt-engine package and run the engine-setup command to configure the engine.

Important

If the upgrade fails, the engine-setup command attempts to rollback your installation to its previous state. Do not remove the repositories required by the 4.2 engine until after the upgrade successfully completes. If you encounter a failed upgrade, detailed instructions display explaining how to restore your installation.

  1. Subscribe to the required channels OR install the Release 4.3.6 package.

    • For ULN registered hosts only: If the host is registered on ULN, subscribe the system to the required channels.

      1. Log in to https://linux.oracle.com with your ULN user name and password.

      2. On the Systems tab, click the link named for the host in the list of registered machines.

      3. On the System Details page, click Manage Subscriptions.

      4. On the System Summary page, select each required channel from the list of available channels and click the right arrow to move the channel to the list of subscribed channels. Subscribe the system to the following channels:

        • ol7_x86_64_ovirt43

        • ol7_x86_64_ovirt43_extras

      5. Click Save Subscriptions.

    • For Oracle Linux yum server hosts only: Install the Oracle Linux Virtualization Manager Release 4.3.6 package.

      # yum install oracle-ovirt-release-el7
  2. Check to see if your engine is eligible to upgrade and if there are updates for any packages.

    # engine-upgrade-check
    ...
    Upgrade available.
  3. Update the setup packages and resolve dependencies.

    # yum update ovirt\*setup\*
    ...
    Complete!
  4. Update the engine to Release 4.3.6.

    # engine-setup
    ...
    [ INFO  ] Execution of setup completed successfully

    The engine-setup script 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. For more information about the configuration options, see the Section 2.1.2, “Engine Configuration Options”.

    Note

    When you run the engine-setup script during the installation process your configuration values are stored. During an upgrade, these stored values display when previewing the configuration and they might not be up-to-date if you ran engine-config after installation. For example, if you ran engine-config to update SANWipeAfterDelete to true after installation, engine-setup outputs Default SAN wipe after delete: False in the configuration preview. However, your updated values are not overwritten by engine-setup.

  5. Unsubscribe to the 4.2 channels OR disable the 4.2 repositories.

    • For ULN registered hosts only: If the host is registered on ULN, unsubscribe to the following channels.

      • ol7_x86_64_ovirt42

      • ol7_x86_64_ovirt42_extras

    • For Oracle Linux yum server hosts only: Run the following commands.

      # yum-config-manager --disable ovirt-4.2
      # yum-config-manager --disable ovirt-4.2-extra
      Important

      Before you execute yum-config-manager ensure the yum-utils package is installed on your system. For more information, see Using Yum Utilities to Manage Configuration in Oracle® Linux 7: Managing Software

You are now ready to proceed with Section 4.2, “Upgrading KVM Hosts”.

4.2 Upgrading KVM Hosts

After you upgrade your engine, you have the option of working with Release 4.2.8 KVM hosts or upgrading them to Release 4.3.6. If you choose to upgrade one or more hosts, any virtual machines residing on a host are put into Maintenance mode before the host is upgraded. After the upgrade completes, the virtual machines are restarted on the newly upgraded host.

Before you upgrade a KVM host, here are a few considerations.

  • If migration is enabled at the cluster level, virtual machines are automatically migrated to another host in the cluster.

  • The cluster must contan more than one host before performing an upgrade.

  • Do not attempt to upgrade all hosts at the same time because one host must remain available to perform Storage Pool Manager (SPM) tasks.

  • The cluster must have sufficient memory reserve in order for its hosts to perform maintenance. If a cluster lacks sufficient memory, the virtual machine migration hangs and then fails. You can reduce the memory usage of virtual machine migration by shutting down some or all virtual machines before updating the host.

  • You cannot migrate a virtual machine using a vGPU to a different host. Virtual machines with vGPUs installed must be shut down before updating the host.

To upgrade a KVM host you install the ovirt-engine package and then complete the upgrade steps in the Administration Portal.

  1. Subscribe to the required channels OR install the Release 4.3.6 package.

    1. For ULN registered hosts only: If the host is registered on ULN, subscribe the system to the required channels.

      1. Log in to https://linux.oracle.com with your ULN user name and password.

      2. On the Systems tab, click the link named for the host in the list of registered machines.

      3. On the System Details page, click Manage Subscriptions.

      4. On the System Summary page, select each required channel from the list of available channels and click the right arrow to move the channel to the list of subscribed channels. Subscribe the system to the following channels:

        • ol7_x86_64_ovirt43

        • ol7_x86_64_ovirt43_extras

      5. Click Save Subscriptions.

    2. For Oracle Linux yum server hosts only: Install the Oracle Linux Virtualization Manager Release 4.3.6 package.

      # yum install oracle-ovirt-release-el7
  2. In the Administration portal, go to Compute and then click Hosts.

  3. In the Hosts pane, select a host, click Installation and then Check for Upgrade.

  4. From the Upgrade Host window, click OK.

    The engine checks the KVM host to see if it requires an upgrade.

  5. To proceed with the upgrade, click Installation and then Upgrade.

  6. From the Upgrade Host window, click OK to begin the upgrade process.

    On the Hosts pane you can watch the host transition through the upgrade stages: Maintenance, Installing, Up. The host is rebooted after the upgrade and displays a status of Up if successful. If any virtual machines were migrated off the host, they are migrated back.

    Note

    If the update fails, the host’s status changes to Install Failed and you must click Installation and then Upgrade again.

  7. Unsubscribe to the 4.2 channels OR disable the 4.2 repositories.

    1. For ULN registered hosts only: If the host is registered on ULN, unsubscribe to the following channels.

      • ol7_x86_64_ovirt42

      • ol7_x86_64_ovirt42_extras

    2. For Oracle Linux yum server hosts only: Run the following commands.

      # yum-config-manager --disable ovirt-4.2
      # yum-config-manager --disable ovirt-4.2-extra
      Important

      Before you execute yum-config-manager ensure the yum-utils package is installed on your system. For more information, see Using Yum Utilities to Manage Configuration in Oracle® Linux 7: Managing Software

  8. (Optional) Repeat the previous steps for any KVM host in your environment that you want to upgrade.

4.3 Post-Upgrade Data Center and Cluster Compatibility Versions

Oracle Linux Virtualization Manager data centers and clusters have a compatibility version. The data center compatibility version indicates the version of Oracle Linux Virtualization Manager that the data center is intended to be compatible with. The cluster compatibility version indicates the features supported by all of the hosts in the cluster. The cluster compatibility is set according to the version of the least capable host operating system in the cluster.

4.3.1 About Compatibility Versions

To ensure you do not have issues with compatibility versions after you upgrade, keep in mind the following.

  • The data center compatibility level is the minimum version you can use for all clusters in your data center. For example:

    • If your data center compatibility level is 4.3, you can only have 4.3 compatibility level clusters.

    • If your data center compatibility level is 4.2, you can have 4.2 and 4.3 compatibility level clusters.

  • The cluster compatibility level is the minimum version of any host you add to the cluster. For example:

    • If you have a 4.2 compatibility version cluster, you can add 4.2 or 4.3 hosts.

    • If you have a 4.3 compatibility version cluster, you can only add 4.3 hosts.

  • If you try to change the cluster compatibility version from 4.2 to 4.3 when you have 4.2 hosts running, you get the following error:

    [Error while executing action: Cannot change Cluster Compatibility Version to higher version 
    when there are active Hosts with lower version. -Please move Host [hostname] with lower 
    version to maintenance first.]
  • If you try to change the data center compatibility version from 4.2 to 4.3 when you have a 4.2 compatibility version cluster, you get the following error:

    [Cannot update Data Center compatibility version to a value that is greater than its 
    cluster's version. The following clusters should be upgraded: [clustername]]
  • When you put a 4.2 host in maintenance mode, you can change the cluster and then data center compatibility version to 4.3. However, the host shows non-operational with the following event:

    [ Host [hostname] is compatible with versions (3.6,4.0,4.1,4.2) and cannot join Cluster 
    [clustername] which is set to version 4.3.]
  • If you attempt to add a new 4.2 host to a 4.3 engine you might get an error message in the ansible log similar to the following:

    [ValueError: need more than 1 value to unpack.]

    To resolve this error, log onto the host as root and execute the following two commands and then attempt to add the host to the engine again.

    # sed 's|enabled=1|enabled=0|g' /etc/yum/pluginconf.d/enabled_repos_upload.conf -i 
    # sed 's|enabled=1|enabled=0|g' /etc/yum/pluginconf.d/package_upload.conf -i

Note

The preferred approach after upgrading your engine to 4.3 is to upgrade all hosts to 4.3 and then change the cluster compatibility to 4.3. You can then add new hosts as 4.3 hosts.

4.3.2 Changing Cluster and Data Center Compatibility Versions

To change the cluster compatibility version, you must have first upgraded all the hosts in your cluster to a level that supports your desired compatibility level. To change the data center compatibility version, you must have first upgraded all the clusters in your data center to a level that supports your desired compatibility level.

Complete the following steps to change a cluster's compatibility version:

  1. In the Administration Portal, go to Compute and click Clusters.

  2. Select the cluster to change and click Edit.

  3. From the Edit Cluster dialog box, select General.

  4. For Compatibility Version, select desired value and click OK.

  5. On the Change Cluster Compatibility Version confirmation window, click OK.

    Important

    You might get an error message warning that some virtual machines and templates are incorrectly configured. To fix this error, edit each virtual machine manually. The Edit Virtual Machine window provides additional validations and warnings that show what to correct. Sometimes the issue is automatically corrected and the virtual machine’s configuration just needs to be saved again. After editing each virtual machine, you will be able to change the cluster compatibility version.

  6. Update the cluster compatibility version of all running or suspended virtual machines by restarting them from within the Administration Portal.

    Note

    Virtual machines continue to run in the previous cluster compatibility level until they are restarted. Those virtual machines that require a restart are marked with the Next-Run icon (triangle with an exclamation mark). However, the self-hosted engine virtual machine does not need to be restarted.

    You cannot change the cluster compatibility version of a virtual machine snapshot that is in preview; you must first commit or undo the preview.

Now that you have updated the compatibility version of all clusters in a data center, you can change the compatibility version of the data center itself. To do this, complete the following steps:

  1. In the Administration Portal, go to Compute and click Data Centers.

  2. Select the data center to change and click Edit.

  3. From the Edit Data Center dialog box, change the Compatibility Version to the desired value and then click OK.

  4. On the Change Data Center Compatibility Version confirmation window, click OK.

The compatibility version of the data center is now updated.