Chapter 5. Update between minor releases

1. Click the Tasks tab at the bottom right of the Manager. Ensure that there are no ongoing tasks related to data synchronization. If data synchronization tasks are present, wait until they are complete before starting the update process.

2. Remove all the scheduled geo-replication sessions so that synchronization will not occur during the update.

   1. Click Storage Domains Select the domain and click on the domain name.
   2. Click the Remote Data Sync Setup tab Setup button.
   3. New dialog window to set the geo-replication schedule pops-up,set the recurrence to None.

1. Place the cluster into Global Maintenance mode.

   1. Log in to the Web Console of one of the hyperconverged nodes.
   2. Click Virtualization Hosted Engine.
   3. Click Put this cluster into global maintenance.

2. On the Manager machine, check if updated packages are available. Log in to the Hosted Engine Virtual Machine and run the following command:

   # engine-upgrade-check

1. Log in to the Hosted Engine virtual machine.

2. Upgrade the setup packages using the following command:

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

3. Update the Red Hat Virtualization Manager with the engine-setup script. The engine-setup script performs the following tasks:

   • Prompts you with configuration questions.
   • Stops the ovirt-engine service.
   • Downloads and installs the updated packages.
   • Backs up and updates the database.
   • Performs post-installation configuration,

   • Starts the ovirt-engine service.

     1. Run the engine-setup script and follow the prompts to upgrade the Manager. This process can take a while and cannot be aborted, Red Hat recommends running it inside a tmux session.

        # engine-setup

        When the script completes successfully, the following message appears:

        Execution of setup completed successfully.

   Important

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

4. Upgrade all other packages.

   # yum update

   Important

   If any kernel packages are updated:

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

5. Remove the cluster from Global Maintenance mode.

   1. Log in to the Web Console of one of the hyperconverged nodes
   2. Click Virtualization Hosted Engine.
   3. Click Remove this cluster from maintenance.

1. Upgrade each hyperconverged host in the cluster, one at a time.

   For each hyperconverged host in the cluster:

   1. Upgrade the hyperconverged host.

      1. In the Manager, click Compute Hosts and select a node.
      2. Click Installation Upgrade.

      3. Click OK to confirm the upgrade.

         The node is upgraded and rebooted.

   2. Verify self-healing is complete.

      1. Click the name of the host.
      2. Click the Bricks tab.
      3. Verify that the Self-Heal Info column shows OK beside all bricks.

2. Update cluster compatibility settings to ensure you can use new features.

   1. Log in to the Administrator Portal.
   2. Click Cluster and select the cluster name (Default).
   3. Click Edit.

   4. Change Cluster compatibility version to 4.6.

      Important

      Cluster compatibility is not completely updated until the virtual machines have been rebooted. Schedule a maintenance window and move any application virtual machines to maintenance mode before rebooting all virtual machines on each node.

   5. Click Compute Data Centers.
   6. Click Edit.
   7. Change Compatibility version to 4.6.

3. Update data center compatibility settings to ensure you can use new features.

   1. Select Compute Data Centers.
   2. Select the appropriate data center.
   3. Click Edit.
   4. The Edit Data Center dialog box opens.
   5. Update Compatibility Version to 4.6 from the dropdown list.

1. In the Manager, click Compute Hosts and select a node.
2. Click Installation Check for Upgrade. This will trigger a background check on that host for the presence of host update.
3. Once the update is available, there will be a notification next to the host about the availability of host update.

4. Move the host to maintenance mode.

   1. On the RHV Administration Portal, navigate to Hosts Select the host.
   2. Click on Management Maintenance Maintenance Host dialog box opens.
   3. On the Maintenance Host dialog box, check the Stop Gluster service box click OK.

5. Once the host is in maintenance mode, click Installation Upgrade.

   Upgrade Host dialog box opens, make sure to un-check Reboot host after upgrade.

6. Click OK to confirm the upgrade.
7. Wait for the upgrade to complete.

8. Remove the existing LVM filter on the upgraded host before rebooting by using the following command:

   # sed -i /^filter/d /etc/lvm/lvm.conf

9. Reboot the host.

10. Once the host is rebooted, regenerate the LVM filter:

    # vdsm-tool config-lvm-filter -y

11. Verify self-healing is complete before upgrading the next host.

    1. Click the name of the host.
    2. Click the Bricks tab.
    3. Verify that the Self-Heal information column of all bricks is listed as OK before upgrading the next host.
12. Repeat the above steps on the other hyperconverged hosts.

13. Update cluster compatibility settings to ensure you can use new features.

    1. Log in to the Administrator Portal.
    2. Click Cluster and select the cluster name (Default).
    3. Click Edit.

    4. Change Cluster compatibility version to 4.6.

       Important

       Cluster compatibility is not completely updated until the virtual machines have been rebooted. Schedule a maintenance window and move any application virtual machines to maintenance mode before rebooting all virtual machines on each node.

    5. Click Compute Data Centers.
    6. Click Edit.
    7. Change Compatibility version to 4.6.

14. Update data center compatibility settings to ensure you can use new features.

    1. Select Compute Data Centers.
    2. Select the appropriate data center.
    3. Click Edit.
    4. The Edit Data Center dialog box opens.
    5. Update Compatibility Version to 4.6 from the dropdown list.

Troubleshooting

1. The self healing process should start automatically once each hyperconverged host comes up after a reboot. Check for self-heal status using the command:

   # gluster volume heal <volname> info summary

   If there are pending self-heal entries for a long time, check the following:

   1. Gluster network is up.

      # ip addr show <ethernet-interface>

   2. All brick processes in the volume are up.

      # gluster volume status <vol>

      If there are any brick processes reported to be down, restart the glusterd service on the node where the brick is reported to be down:

      # systemctl restart glusterd

2. If the Red Hat Virtualization node is unable to boot and drops in to maintenance shell, then one of the reasons is due to the unstable LVM filter rejecting some of the physical volumes (PVs).

   1. Log into the maintenance shell with the root password.

   2. Remove the existing LVM filter configuration:

      # sed -i /^filter/d /etc/lvm/lvm.conf

   3. Reboot the host.

   4. Once the node is up, regenerate the LVM filter:

      # vdsm-tool config-lvm-filter -y