Chapter 3. Upgrading a standalone Manager remote database environment

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 the Manager machine.

2. Back up the Red Hat Virtualization Manager 4.3 environment.

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

3. Copy the backup file to a storage device outside of the RHV environment.
4. Install Red Hat Enterprise Linux 8.6. See Performing a standard RHEL installation for more information.
5. Complete the steps to install Red Hat Virtualization Manager 4.4, including running the command yum install rhvm, but do not run engine-setup. See one of the Installing Red Hat Virtualization guides for more information.

6. Copy the backup file to the Red Hat Virtualization Manager 4.4 machine and restore it.

   # engine-backup --mode=restore --file=backup.bck --provision-all-databases

   Note

   If the backup contained grants for extra database users, this command creates 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.

7. Ensure the Manager has the correct repositories enabled. For the list of required repositories, see Enabling the Red Hat Virtualization Manager Repositories for Red Hat Virtualization 4.4.

   Updates to the Red Hat Virtualization Manager are released through the Content Delivery Network.

8. Install optional extension packages if they were installed on the Red Hat Virtualization Manager 4.3 machine.

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

   Note

   The ovirt-engine-extension-aaa-ldap is deprecated. For new installations, use Red Hat Single Sign On. For more information, see Installing and Configuring Red Hat Single Sign-On in the Administration Guide.

   Note

   The configuration for these package extensions must be manually reapplied because they are not migrated as part of the backup and restore process.

9. Configure the Manager by running the engine-setup command:

   # engine-setup

10. Decommission the Red Hat Virtualization Manager 4.3 machine if a different machine is used for Red Hat Virtualization Manager 4.4. Two different Managers must not manage the same hosts or storage.

Procedure

1. Back up the Data Warehouse machine.

   Note

   Grafana is not supported on RHV 4.3, but on RHV 4.4, this command also includes the Grafana service and the Grafana database.

   # engine-backup --file=<backupfile>

2. Copy the backup file to a storage device.

3. Stop and disable the Data Warehouse service:

   # systemctl stop ovirt-engine-dwhd
   # systemctl disable ovirt-engine-dwhd

4. Reinstall the Data Warehouse machine with Red Hat Enterprise Linux 8.6, or Red Hat Virtualization Host 4.4.
5. Prepare a PostgreSQL database. For information, see Preparing a Remote PostgreSQL Database in Installing Red Hat Virtualization as a standalone Manager with remote databases.
6. Enable the correct repositories on the server and install the Data Warehouse service. For detailed instructions, see Installing and Configuring Data Warehouse on a Separate Machine for Red Hat Virtualization 4.4. Complete the steps in that procedure up to and including the dnf install ovirt-engine-dwh-setup command. Then continue to the next step in this procedure.
7. Copy the backup file from the storage device to the Data Warehouse machine.

8. Restore the backup file:

   # engine-backup --mode=restore --file=backup.bck --provision-all-databases

9. On the Data Warehouse machine, run the engine-setup command:

   # engine-setup

10. On the Manager machine, restart the Manager to connect it to the Data Warehouse database:

    # systemctl restart ovirt-engine

Procedure

1. Pick a host to upgrade and migrate that host’s virtual machines to another host in the same cluster. You can use Live Migration to minimize virtual machine downtime. For more information, see Migrating Virtual Machines Between Hosts in the Virtual Machine Management Guide.
2. Put the host into maintenance mode and remove the host from the Manager. For more information, see Removing a Host in the Administration Guide.
3. Install Red Hat Enterprise Linux 8.6, or RHVH 4.4. For more information, see Installing Hosts for Red Hat Virtualization in one of the Installing Red Hat Virtualization guides.
4. Install the appropriate packages to enable the host for RHV 4.4. For more information, see Installing Hosts for Red Hat Virtualization in one of the Installing Red Hat Virtualization guides.
5. Add this host to the Manager, assigning it to the same cluster. You can now migrate virtual machines onto this host. For more information, see Adding Standard Hosts to the Manager in one of the Installing Red Hat Virtualization guides.

Procedure

1. Ensure that the local storage on the RHVH 4.3 host’s local storage is in maintenance mode before starting this process. Complete these steps:

   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 references in Red Hat Enterprise Linux 8 Performing an advanced RHEL installation.

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 Standard Hosts to the Red Hat Virtualization Manager in one of the Installing Red Hat Virtualization guides 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.
12. Set the name to localfs and set the path to /localfs.
13. Once the local storage is active, click Import Domain and set the domain’s details. For example, define Data as the name, Local on Host as the storage type and /data as the path.
14. Click OK to confirm the message that appears informing you that storage domains are already attached to the data center.

15. 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.

16. 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 machines and click Import. See Importing Virtual Machines from a Data Domain in the Virtual Machine Management Guide for more details.
17. Once you have ensured that all virtual machines have been successfully imported and are functioning properly, you can move localfs to maintenance mode.

18. Click the Storage tab and select localfs from the results list.

    1. Click the Data Center tab in the details pane.
    2. Click Maintenance, then click OK to move the storage domain to maintenance mode.
    3. Click Detach. The Detach Storage confirmation window opens.
    4. Click OK.

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.