Chapter 4. Updates between minor releases

Procedure

1. Install the Log Collection Analysis tool on the Manager machine:

   # yum install rhv-log-collector-analyzer

2. Run the tool:

   # rhv-log-collector-analyzer --live

   A detailed report is displayed.

   By default, the report is saved to a file called analyzer_report.html.

   To save the file to a specific location, use the --html flag and specify the location:

   # rhv-log-collector-analyzer --live --html=/directory/filename.html

3. You can use the ELinks text mode web browser to read the analyzer reports within the terminal. To install the ELinks browser:

   # yum install -y elinks

4. Launch ELinks and open analyzer_report.html.

   # elinks /home/user1/analyzer_report.html

   To navigate the report, use the following commands in ELinks:

   • Insert to scroll up
   • Delete to scroll down
   • PageUp to page up
   • PageDown to page down
   • Left Bracket to scroll left
   • Right Bracket to scroll right

Procedure

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

   # engine-upgrade-check

2. Update the setup packages:

   # yum update ovirt\*setup\* rh\*vm-setup-plugins

3. Update the Red Hat Virtualization Manager with the engine-setup script. 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.

   # engine-setup

   When the script completes successfully, the following message appears:

   Execution of setup completed successfully

   Note

   The engine-setup script 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 might 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.

   Important

   The update process might take some time. Do not stop the process before it completes.

4. Update the base operating system and any optional packages installed on the Manager:

   # yum update --nobest

   Important

   If you encounter a required Ansible package conflict during the update, see Cannot perform yum update on my RHV manager (ansible conflict).

   Important

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

Procedure

1. Log in to one of the self-hosted engine nodes and enable global maintenance mode:

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

2. Confirm that the environment is in global maintenance mode before proceeding:

   # hosted-engine --vm-status

   You should see a message indicating that the cluster is in global maintenance mode.

Procedure

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

   # engine-upgrade-check

2. Update the setup packages:

   # yum update ovirt\*setup\* rh\*vm-setup-plugins

3. Update the Red Hat Virtualization Manager with the engine-setup script. 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.

   # engine-setup

   When the script completes successfully, the following message appears:

   Execution of setup completed successfully

   Note

   The engine-setup script 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 might 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.

   Important

   The update process might take some time. Do not stop the process before it completes.

4. Update the base operating system and any optional packages installed on the Manager:

   # yum update --nobest

   Important

   If you encounter a required Ansible package conflict during the update, see Cannot perform yum update on my RHV manager (ansible conflict).

   Important

   If any kernel packages were updated:

   1. Disable global maintenance mode
   2. Reboot the machine to complete the update.

Procedure

1. Log in to the Manager virtual machine and shut it down.

2. Log in to one of the self-hosted engine nodes and disable global maintenance mode:

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

   When you exit global maintenance mode, ovirt-ha-agent starts the Manager virtual machine, and then the Manager automatically starts. It can take up to ten minutes for the Manager to start.

3. Confirm that the environment is running:

   # hosted-engine --vm-status

   The listed information includes Engine Status. The value for Engine status should be:

   {"health": "good", "vm": "up", "detail": "Up"}

   Note

   When the virtual machine is still booting and the Manager hasn’t started yet, the Engine status is:

   {"reason": "bad vm status", "health": "bad", "vm": "up", "detail": "Powering up"}

   If this happens, wait a few minutes and try again.

Procedure

1. In the Administration Portal, click Compute Clusters and select the cluster. The Upgrade status column shows if an upgrade is available for any hosts in the cluster.
2. Click Upgrade.
3. Select the hosts to update, then click Next.

4. Configure the options:

   • Stop Pinned VMs shuts down any virtual machines that are pinned to hosts in the cluster, and is selected by default. You can clear this check box to skip updating those hosts so that the pinned virtual machines stay running, such as when a pinned virtual machine is running important services or processes and you do not want it to shut down at an unknown time during the update.
   • Upgrade Timeout (Minutes) sets the time to wait for an individual host to be updated before the cluster upgrade fails with a timeout. The default is 60. You can increase it for large clusters where 60 minutes might not be enough, or reduce it for small clusters where the hosts update quickly.
   • Check Upgrade checks each host for available updates before running the upgrade process. It is not selected by default, but you can select it if you need to ensure that recent updates are included, such as when you have configured the Manager to check for host updates less frequently than the default.
   • Reboot After Upgrade reboots each host after it is updated, and is selected by default. You can clear this check box to speed up the process if you are sure that there are no pending updates that require a host reboot.
   • Use Maintenance Policy sets the cluster’s scheduling policy to cluster_maintenance during the update. It is selected by default, so activity is limited and virtual machines cannot start unless they are highly available. You can clear this check box if you have a custom scheduling policy that you want to keep using during the update, but this could have unknown consequences. Ensure your custom policy is compatible with cluster upgrade activity before disabling this option.
5. Click Next.
6. Review the summary of the hosts and virtual machines that are affected.
7. Click Upgrade.
8. A cluster upgrade status screen displays with a progress bar showing the precentage of completion, and a list of steps in the upgrade process that have completed. You can click Go to Event Log to open the log entries for the upgrade. Closing this screen does not interrupt the upgrade process.

Procedure

1. In the Administration Portal, click Compute Clusters.
2. Select the cluster to change and click Edit.
3. On the General tab, change the Compatibility Version to the desired value.
4. Click OK. The Change Cluster Compatibility Version confirmation dialog opens.
5. Click OK to confirm.

Procedure

1. In the Administration Portal, click Compute Virtual Machines.

2. Check which virtual machines require a reboot. In the Vms: search bar, enter the following query:

   next_run_config_exists=True

   The search results show all virtual machines with pending changes.

3. Select each virtual machine and click Restart. Alternatively, if necessary you can reboot a virtual machine from within the virtual machine itself.

Procedure

1. In the Administration Portal, click Compute Data Centers.
2. Select the data center to change and click Edit.
3. Change the Compatibility Version to the desired value.
4. Click OK. The Change Data Center Compatibility Version confirmation dialog opens.
5. Click OK to confirm.

Procedure

1. Ensure that the correct repositories are enabled. To view a list of currently enabled repositories, run dnf repolist.

   • For Red Hat Virtualization Hosts:

     # subscription-manager repos --enable=rhvh-4-for-rhel-8-x86_64-rpms

   • For Red Hat Enterprise Linux hosts:

     # subscription-manager repos \
         --enable=rhel-8-for-x86_64-baseos-eus-rpms \
         --enable=rhel-8-for-x86_64-appstream-eus-rpms \
         --enable=rhv-4-mgmt-agent-for-rhel-8-x86_64-rpms \
         --enable=advanced-virt-for-rhel-8-x86_64-rpms \
         --enable=fast-datapath-for-rhel-8-x86_64-rpms
     
     # subscription-manager release --set=8.6

2. In the Administration Portal, click Compute Hosts and select the host to be updated.

3. Click Installation Check for Upgrade and click OK.

   Open the Notification Drawer ( ) and expand the Events section to see the result.

4. If an update is available, click Installation Upgrade.

5. Click OK to update the host. Running virtual machines are migrated according to their migration policy. If migration is disabled for any virtual machines, you are prompted to shut them down.

   The details of the host are updated in Compute Hosts and the status transitions through these stages:

   Maintenance > Installing > Reboot > Up

   Note

   If the update fails, the host’s status changes to Install Failed. From Install Failed you can click Installation Upgrade again.

Procedure

1. Ensure the correct repositories are enabled. You can check which repositories are currently enabled by running dnf repolist.

   • For Red Hat Virtualization Hosts:

     # subscription-manager repos --enable=rhvh-4-for-rhel-8-x86_64-rpms

   • For Red Hat Enterprise Linux hosts:

     # subscription-manager repos \
         --enable=rhel-8-for-x86_64-baseos-eus-rpms \
         --enable=rhel-8-for-x86_64-appstream-eus-rpms \
         --enable=rhv-4-mgmt-agent-for-rhel-8-x86_64-rpms \
         --enable=advanced-virt-for-rhel-8-x86_64-rpms \
         --enable=fast-datapath-for-rhel-8-x86_64-rpms
     
     # subscription-manager release --set=8.6

2. In the Administration Portal, click Compute Hosts and select the host to be updated.
3. Click Management Maintenance and OK.

4. For Red Hat Enterprise Linux hosts:

   1. Identify the current version of Red Hat Enterprise Linux:

      # cat /etc/redhat-release

   2. Check which version of the redhat-release package is available:

      # dnf --refresh info --available redhat-release

      This command shows any available updates. For example, when upgrading from Red Hat Enterprise Linux 8.2.z to 8.3, compare the version of the package with the currently installed version:

      Available Packages
      Name         : redhat-release
      Version      : 8.3
      Release      : 1.0.el8
      …​

      Caution

      The Red Hat Enterprise Linux Advanced Virtualization module is usually released later than the Red Hat Enterprise Linux y-stream. If no new Advanced Virtualization module is available yet, or if there is an error enabling it, stop here and cancel the upgrade. Otherwise you risk corrupting the host.

   3. If the Advanced Virtualization stream is available for Red Hat Enterprise Linux 8.3 or later, reset the virt module:

      # dnf module reset virt

      Note

      If this module is already enabled in the Advanced Virtualization stream, this step is not necessary, but it has no negative impact.

      You can see the value of the stream by entering:

      # dnf module list virt

   4. Enable the virt module in the Advanced Virtualization stream with the following command:

      • For RHV 4.4.2:

        # dnf module enable virt:8.2

      • For RHV 4.4.3 to 4.4.5:

        # dnf module enable virt:8.3

      • For RHV 4.4.6 to 4.4.10:

        # dnf module enable virt:av

      • For RHV 4.4 and later:

        # dnf module enable virt:rhel

        Note

        Starting with RHEL 8.6 the Advanced virtualization packages will use the standard virt:rhel module. For RHEL 8.4 and 8.5, only one Advanced Virtualization stream is used, rhel:av.

5. Enable version 14 of the nodejs module:

   # dnf module -y enable nodejs:14

6. Update the host:

   # dnf upgrade --nobest

7. Reboot the host to ensure all updates are correctly applied.

   Note

   Check the imgbased logs to see if any additional package updates have failed for a Red Hat Virtualization Host. If some packages were not successfully reinstalled after the update, check that the packages are listed in /var/imgbased/persisted-rpms. Add any missing packages then run rpm -Uvh /var/imgbased/persisted-rpms/*.