Upgrade Guide

On the Engine machine, check if updated packages are available:

# engine-upgrade-check

Update the setup packages:

# dnf update ovirt\*setup\*

Update the oVirt Engine 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

Execution of setup completed successfully

Update the base operating system and any optional packages installed on the Engine:

# yum update --nobest

Enable oVirt 4.5 repositories

# dnf install -y centos-release-ovirt45

Enable oVirt 4.5 repositories

Enable oVirt 4.5 repositories

Follow the procedure for updates between minor releases.

Follow the procedure for updating the cluster compatibility version.

In the Administration Portal, click Compute  Clusters.

Select the cluster to change and click Edit.

On the General tab, change the Compatibility Version to the desired value.

Click OK. The Change Cluster Compatibility Version confirmation dialog opens.

Click OK to confirm.

In the Administration Portal, click Compute  Virtual Machines.

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

next_run_config_exists=True

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

In the Administration Portal, click Compute  Data Centers.

Select the data center to change and click Edit.

Change the Compatibility Version to the desired value.

Click OK. The Change Data Center Compatibility Version confirmation dialog opens.

Click OK to confirm.

On the Engine machine, check if updated packages are available:

# engine-upgrade-check

Update the setup packages:

# dnf update ovirt\*setup\*

Update the oVirt Engine 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

Execution of setup completed successfully

Update the base operating system and any optional packages installed on the Engine:

# yum update --nobest

Log in to the Engine machine.

Back up the oVirt Engine 4.3 environment.

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

Copy the backup file to a storage device outside of the oVirt environment.

Install Enterprise Linux 8.6. See Performing a standard RHEL installation for more information.

Complete the steps to install oVirt Engine 4.4, including running the command yum install rhvm, but do not run engine-setup. See one of the Installing oVirt guides for more information.

Copy the backup file to the oVirt Engine 4.4 machine and restore it.

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

Install optional extension packages if they were installed on the oVirt Engine 4.3 machine.

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

Configure the Engine by running the engine-setup command:

# engine-setup

Decommission the oVirt Engine 4.3 machine if a different machine is used for oVirt Engine 4.4. Two different Engines must not manage the same hosts or storage.

Run engine-setup to configure the Engine.

# engine-setup

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.

Put the host into maintenance mode and remove the host from the Engine. For more information, see Removing a Host in the Administration Guide.

Install Enterprise Linux 8.6, or oVirt Node 4.4. For more information, see Installing Hosts for oVirt in one of the Installing oVirt guides.

Install the appropriate packages to enable the host for oVirt 4.4. For more information, see Installing Hosts for oVirt in one of the Installing oVirt guides.

Add this host to the Engine, assigning it to the same cluster. You can now migrate virtual machines onto this host. For more information, see Adding Standard Hosts to the Engine in one of the Installing oVirt guides.

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

Reinstall the oVirt Node, as described in Installing oVirt Node in the Installation Guide.

# clearpart --all --drives=device

On the reinstalled host, create a directory, for example /data in which to recover the previous environment.

# mkdir /data

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

# mount /dev/sdX1 /data

Set the following permissions for the new directory.

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

oVirt 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

In the Administration Portal, create a data center and select Local in the Storage Type drop-down menu.

Configure a cluster on the new data center. See Creating a New Cluster in the Administration Guide for more information.

Add the host to the Engine. See Adding Standard Hosts to the oVirt Manager in one of the Installing oVirt guides for more information.

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

In the Administration Portal, open the Storage tab and click New Domain to create a new local storage domain.

Set the name to localfs and set the path to /localfs.

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.

Click OK to confirm the message that appears informing you that storage domains are already attached to the data center.

Activate the new storage domain:

Once the new storage domain is active, import the virtual machines and their disks:

Once you have ensured that all virtual machines have been successfully imported and are functioning properly, you can move localfs to maintenance mode.

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

Create a new Gluster volume for oVirt Node 4.4 Engine deployment.

Back up the Gluster configuration on all oVirt Node 4.3 nodes using the backup playbook.

Using the Manager Administration Portal, migrate the VMs running on the first host to other hosts in the cluster.

Backup Engine configurations.

# engine-backup --mode=backup --scope=all --file=<backup-file.tar.gz> --log=<logfile>

Check for any pending self-heal tasks on all the replica 3 volumes. Wait for the heal to be completed.

Run the following command on one of the hosts:

# gluster volume heal <volume> info summary

Stop the glusterfs brick process and unmount all the bricks on the first host to maintain file system consistency. Run the following on the first host:

# pkill glusterfsd; pkill glusterfs
# systemctl stop glusterd
# umount /gluster_bricks/*

Reinstall the host with oVirt Node 4.4 ISO, only formatting the OS disk.

Once the node is up following the oVirt Node 4.4 installation reboot, subscribe to oVirt Node 4.4 repos as outlined in the Installation Guide, or install the downloaded oVirt Node 4.4 appliance.

# yum install <appliance>

Disable the devices used for Gluster bricks.

Copy the Engine backup and host config tar files from the backup host to the newly installed host and untar the content using scp.

Restore the Gluster configuration files.

Perform Engine deployment with the option --restore-from-file pointing to the backed-up archive from the Engine. This Engine deployment can be done interactively using the hosted-engine --deploy command, providing the storage corresponds to the newly created Engine volume. The same can also be done using ovirt-ansible-hosted-engine-setup in an automated procedure. The following procedure is an automated method for deploying a HostedEngine VM using the backup:

Log in to the oVirt Node 4.4 Administration Portal on the newly installed oVirt manager. Make sure all the hosts are in the ‘up’ state, and wait for the self-heal on the Gluster volumes to be completed.

Upgrade the next host

Repeat the step Upgrade the next host for all the oVirt Node in the cluster.

(optional) If a separate Gluster logical network exists in the cluster, attach the Gluster logical network to the required interface on each host.

Remove the old Engine storage domain. Identify the old Engine storage domain by the name hosted_storage with no gold star next to it, listed under Storage  Domains.

Stop and remove the old Engine volume.

Update the cluster compatibility version.

There are new Gluster volume options available with oVirt Node 4.4, apply those volume options on all the volumes. Execute the following on one of the nodes in the cluster:

# for vol in gluster volume list; do gluster volume set $vol group virt; done

Remove the archives and extracted the contents of the backup configuration files on all nodes.

Log in to the Engine web console.

Go to Virtualization  Hosted Engine and click Manage Gluster.

Click Create Volume. In the Create Volume window, do the following:

In the Administration Portal, click Compute  Clusters.

Select the cluster to change and click Edit.

On the General tab, change the Compatibility Version to the desired value.

Click OK. The Change Cluster Compatibility Version confirmation dialog opens.

Click OK to confirm.

In the Administration Portal, click Compute  Virtual Machines.

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

next_run_config_exists=True

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

In the Administration Portal, click Compute  Data Centers.

Select the data center to change and click Edit.

Change the Compatibility Version to the desired value.

Click OK. The Change Data Center Compatibility Version confirmation dialog opens.

Click OK to confirm.

On the Engine machine, check if updated packages are available:

# engine-upgrade-check

Update the setup packages:

# dnf update ovirt\*setup\*

Update the oVirt Engine 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

Execution of setup completed successfully

Update the base operating system and any optional packages installed on the Engine:

# yum update --nobest

Enable the oVirt 4.3 repositories:

# yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm

Update the setup packages:

# yum update ovirt\*setup\*

Run engine-setup and follow the prompts to upgrade the oVirt Engine:

# engine-setup

Execution of setup completed successfully

Update the base operating system:

# yum update

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.

Click Upgrade.

Select the hosts to update, then click Next.

Configure the options:

Click Next.

Review the summary of the hosts and virtual machines that are affected.

Click Upgrade.

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.

In the Administration Portal, click Compute  Clusters.

Select the cluster to change and click Edit.

On the General tab, change the Compatibility Version to the desired value.

Click OK. The Change Cluster Compatibility Version confirmation dialog opens.

Click OK to confirm.

In the Administration Portal, click Compute  Virtual Machines.

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

next_run_config_exists=True

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

In the Administration Portal, click Compute  Data Centers.

Select the data center to change and click Edit.

Change the Compatibility Version to the desired value.

Click OK. The Change Data Center Compatibility Version confirmation dialog opens.

Click OK to confirm.

Log in to the Engine machine as the root user.

Check whether /etc/pki/ovirt-engine/openssl.conf includes the line default_md = sha256:

# cat /etc/pki/ovirt-engine/openssl.conf

# cp -p /etc/pki/ovirt-engine/openssl.conf /etc/pki/ovirt-engine/openssl.conf."$(date +"%Y%m%d%H%M%S")"
# sed -i 's/^default_md = sha1/default_md = sha256/' /etc/pki/ovirt-engine/openssl.conf

Define the certificate that should be re-signed:

# names="apache"

On the Engine, save a backup of the /etc/ovirt-engine/engine.conf.d and /etc/pki/ovirt-engine directories, and re-sign the certificates:

# . /etc/ovirt-engine/engine.conf.d/10-setup-protocols.conf
# for name in $names; do
    subject="$(
        openssl \
            x509 \
            -in /etc/pki/ovirt-engine/certs/"${name}".cer \
            -noout \
            -subject \
            -nameopt compat \
        | sed \
            's;subject=\(.*\);\1;' \
    )"
   /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
        --name="${name}" \
        --password=mypass \ <1>
        --subject="${subject}" \
        --san=DNS:"${ENGINE_FQDN}" \
        --keep-key
done

Restart the httpd service:

# systemctl restart httpd

Connect to the Administration Portal to confirm that the warning no longer appears.

If you previously imported a CA or https certificate into the browser, find the certificate(s), remove them from the browser, and reimport the new CA certificate. Install the certificate authority according to the instructions provided by your browser. To get the certificate authority’s certificate, navigate to http://your-manager-fqdn/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA, replacing your-manager-fqdn with the fully qualified domain name (FQDN).

Log in to the Engine machine as the root user.

Check whether /etc/pki/ovirt-engine/openssl.conf includes the line default_md = sha256:

# cat /etc/pki/ovirt-engine/openssl.conf

# cp -p /etc/pki/ovirt-engine/openssl.conf /etc/pki/ovirt-engine/openssl.conf."$(date +"%Y%m%d%H%M%S")"
# sed -i 's/^default_md = sha1/default_md = sha256/' /etc/pki/ovirt-engine/openssl.conf

Re-sign the CA certificate by backing it up and creating a new certificate in ca.pem.new:

# cp -p /etc/pki/ovirt-engine/private/ca.pem /etc/pki/ovirt-engine/private/ca.pem."$(date +"%Y%m%d%H%M%S")"
# openssl x509 -signkey /etc/pki/ovirt-engine/private/ca.pem -in /etc/pki/ovirt-engine/ca.pem -out /etc/pki/ovirt-engine/ca.pem.new -days 3650 -sha256

Replace the existing certificate with the new certificate:

# mv /etc/pki/ovirt-engine/ca.pem.new /etc/pki/ovirt-engine/ca.pem

Define the certificates that should be re-signed:

# names="engine apache websocket-proxy jboss imageio-proxy"

# names="engine websocket-proxy jboss imageio-proxy"

On the Engine, save a backup of the /etc/ovirt-engine/engine.conf.d and /etc/pki/ovirt-engine directories, and re-sign the certificates:

# . /etc/ovirt-engine/engine.conf.d/10-setup-protocols.conf
# for name in $names; do
    subject="$(
        openssl \
            x509 \
            -in /etc/pki/ovirt-engine/certs/"${name}".cer \
            -noout \
            -subject \
            -nameopt compat \
        | sed \
            's;subject=\(.*\);\1;' \
    )"
   /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
        --name="${name}" \
        --password=mypass \ <1>
        --subject="${subject}" \
        --san=DNS:"${ENGINE_FQDN}" \
        --keep-key
done

Restart the following services:

# systemctl restart httpd
# systemctl restart ovirt-engine
# systemctl restart ovirt-websocket-proxy
# systemctl restart ovirt-imageio

Connect to the Administration Portal to confirm that the warning no longer appears.

If you previously imported a CA or https certificate into the browser, find the certificate(s), remove them from the browser, and reimport the new CA certificate. Install the certificate authority according to the instructions provided by your browser. To get the certificate authority’s certificate, navigate to http://your-manager-fqdn/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA, replacing your-manager-fqdn with the fully qualified domain name (FQDN).

Enroll the certificates on the hosts. Repeat the following procedure for each host.

On the Engine machine, check if updated packages are available:

# engine-upgrade-check

Update the setup packages:

# dnf update ovirt\*setup\*

Update the oVirt Engine 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

Execution of setup completed successfully

Update the base operating system and any optional packages installed on the Engine:

# yum update --nobest

Enable oVirt 4.5 repositories

# dnf install -y centos-release-ovirt45

Enable oVirt 4.5 repositories

Enable oVirt 4.5 repositories

Follow the procedure for updates between minor releases.

Follow the procedure for updating the cluster compatibility version.

In the Administration Portal, click Compute  Clusters.

Select the cluster to change and click Edit.

On the General tab, change the Compatibility Version to the desired value.

Click OK. The Change Cluster Compatibility Version confirmation dialog opens.

Click OK to confirm.

In the Administration Portal, click Compute  Virtual Machines.

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

next_run_config_exists=True

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

In the Administration Portal, click Compute  Data Centers.

Select the data center to change and click Edit.

Change the Compatibility Version to the desired value.

Click OK. The Change Data Center Compatibility Version confirmation dialog opens.

Click OK to confirm.

On the Engine machine, check if updated packages are available:

# engine-upgrade-check

Update the setup packages:

# dnf update ovirt\*setup\*

Update the oVirt Engine 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

Execution of setup completed successfully

Update the base operating system and any optional packages installed on the Engine:

# yum update --nobest

Log in to the Engine machine.

Back up the oVirt Engine 4.3 environment.

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

Copy the backup file to a storage device outside of the oVirt environment.

Install Enterprise Linux 8.6. See Performing a standard RHEL installation for more information.

Complete the steps to install oVirt Engine 4.4, including running the command yum install rhvm, but do not run engine-setup. See one of the Installing oVirt guides for more information.

Copy the backup file to the oVirt Engine 4.4 machine and restore it.

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

Install optional extension packages if they were installed on the oVirt Engine 4.3 machine.

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

Configure the Engine by running the engine-setup command:

# engine-setup

Decommission the oVirt Engine 4.3 machine if a different machine is used for oVirt Engine 4.4. Two different Engines must not manage the same hosts or storage.

Back up the Data Warehouse machine.

# engine-backup --file=<backupfile>

Copy the backup file to a storage device.

Stop and disable the Data Warehouse service:

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

Reinstall the Data Warehouse machine with Enterprise Linux 8.6, or oVirt Node 4.4.

Prepare a PostgreSQL database. For information, see Preparing a Remote PostgreSQL Database in Installing oVirt as a standalone Engine with remote databases.

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

Copy the backup file from the storage device to the Data Warehouse machine.

Restore the backup file:

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

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

# engine-setup

On the Engine machine, restart the Engine to connect it to the Data Warehouse database:

# systemctl restart ovirt-engine

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.

Put the host into maintenance mode and remove the host from the Engine. For more information, see Removing a Host in the Administration Guide.

Install Enterprise Linux 8.6, or oVirt Node 4.4. For more information, see Installing Hosts for oVirt in one of the Installing oVirt guides.

Install the appropriate packages to enable the host for oVirt 4.4. For more information, see Installing Hosts for oVirt in one of the Installing oVirt guides.

Add this host to the Engine, assigning it to the same cluster. You can now migrate virtual machines onto this host. For more information, see Adding Standard Hosts to the Engine in one of the Installing oVirt guides.

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

Reinstall the oVirt Node, as described in Installing oVirt Node in the Installation Guide.

# clearpart --all --drives=device

On the reinstalled host, create a directory, for example /data in which to recover the previous environment.

# mkdir /data

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

# mount /dev/sdX1 /data

Set the following permissions for the new directory.

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

oVirt 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

In the Administration Portal, create a data center and select Local in the Storage Type drop-down menu.

Configure a cluster on the new data center. See Creating a New Cluster in the Administration Guide for more information.

Add the host to the Engine. See Adding Standard Hosts to the oVirt Manager in one of the Installing oVirt guides for more information.

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

In the Administration Portal, open the Storage tab and click New Domain to create a new local storage domain.

Set the name to localfs and set the path to /localfs.

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.

Click OK to confirm the message that appears informing you that storage domains are already attached to the data center.

Activate the new storage domain:

Once the new storage domain is active, import the virtual machines and their disks:

Once you have ensured that all virtual machines have been successfully imported and are functioning properly, you can move localfs to maintenance mode.

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

In the Administration Portal, click Compute  Clusters.

Select the cluster to change and click Edit.

On the General tab, change the Compatibility Version to the desired value.

Click OK. The Change Cluster Compatibility Version confirmation dialog opens.

Click OK to confirm.

In the Administration Portal, click Compute  Virtual Machines.

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

next_run_config_exists=True

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

In the Administration Portal, click Compute  Data Centers.

Select the data center to change and click Edit.

Change the Compatibility Version to the desired value.

Click OK. The Change Data Center Compatibility Version confirmation dialog opens.

Click OK to confirm.

On the Engine machine, check if updated packages are available:

# engine-upgrade-check

Update the setup packages:

# dnf update ovirt\*setup\*

Update the oVirt Engine 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

Execution of setup completed successfully

Update the base operating system and any optional packages installed on the Engine:

# yum update --nobest

Stop the service running on the machine:

Enable the required repository to receive the PostgreSQL 10 package:

Install the PostgreSQL 10 packages:

# yum install rh-postgresql10 rh-postgresql10-postgresql-contrib

Stop and disable the PostgreSQL 9.5 service:

# systemctl stop rh-postgresql95-postgresql
# systemctl disable rh-postgresql95-postgresql

Upgrade the PostgreSQL 9.5 database to PostgreSQL 10:

# scl enable rh-postgresql10 -- postgresql-setup --upgrade-from=rh-postgresql95-postgresql --upgrade

Start and enable the rh-postgresql10-postgresql.service and check that it is running:

# systemctl start rh-postgresql10-postgresql.service
# systemctl enable rh-postgresql10-postgresql.service
# systemctl status rh-postgresql10-postgresql.service

rh-postgresql10-postgresql.service - PostgreSQL database server
   Loaded: loaded (/usr/lib/systemd/system/rh-postgresql10-postgresql.service;
enabled; vendor preset: disabled)
   Active: active (running) since ...

Copy the pg_hba.conf client configuration file from the PostgreSQL 9.5 environment to the PostgreSQL 10 environment:

# cp -p /var/opt/rh/rh-postgresql95/lib/pgsql/data/pg_hba.conf  /var/opt/rh/rh-postgresql10/lib/pgsql/data/pg_hba.conf

Update the following parameters in /var/opt/rh/rh-postgresql10/lib/pgsql/data/postgresql.conf:

listen_addresses='*'
autovacuum_vacuum_scale_factor=0.01
autovacuum_analyze_scale_factor=0.075
autovacuum_max_workers=6
maintenance_work_mem=65536
max_connections=150
work_mem = 8192

Restart the PostgreSQL 10 service to apply the configuration changes:

# systemctl restart rh-postgresql10-postgresql.service

Enable the oVirt 4.3 repositories:

# yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm

Update the setup packages:

# yum update ovirt\*setup\*

Run engine-setup and follow the prompts to upgrade the oVirt Engine, the remote database or remote service:

# engine-setup

Execution of setup completed successfully

Update the base operating system:

# yum update

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.

Click Upgrade.

Select the hosts to update, then click Next.

Configure the options:

Click Next.

Review the summary of the hosts and virtual machines that are affected.

Click Upgrade.

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.

In the Administration Portal, click Compute  Clusters.

Select the cluster to change and click Edit.

On the General tab, change the Compatibility Version to the desired value.

Click OK. The Change Cluster Compatibility Version confirmation dialog opens.

Click OK to confirm.

In the Administration Portal, click Compute  Virtual Machines.

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

next_run_config_exists=True

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

In the Administration Portal, click Compute  Data Centers.

Select the data center to change and click Edit.

Change the Compatibility Version to the desired value.

Click OK. The Change Data Center Compatibility Version confirmation dialog opens.

Click OK to confirm.

Log in to the Engine machine as the root user.

Check whether /etc/pki/ovirt-engine/openssl.conf includes the line default_md = sha256:

# cat /etc/pki/ovirt-engine/openssl.conf

# cp -p /etc/pki/ovirt-engine/openssl.conf /etc/pki/ovirt-engine/openssl.conf."$(date +"%Y%m%d%H%M%S")"
# sed -i 's/^default_md = sha1/default_md = sha256/' /etc/pki/ovirt-engine/openssl.conf

Define the certificate that should be re-signed:

# names="apache"

On the Engine, save a backup of the /etc/ovirt-engine/engine.conf.d and /etc/pki/ovirt-engine directories, and re-sign the certificates:

# . /etc/ovirt-engine/engine.conf.d/10-setup-protocols.conf
# for name in $names; do
    subject="$(
        openssl \
            x509 \
            -in /etc/pki/ovirt-engine/certs/"${name}".cer \
            -noout \
            -subject \
            -nameopt compat \
        | sed \
            's;subject=\(.*\);\1;' \
    )"
   /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
        --name="${name}" \
        --password=mypass \ <1>
        --subject="${subject}" \
        --san=DNS:"${ENGINE_FQDN}" \
        --keep-key
done

Restart the httpd service:

# systemctl restart httpd

Connect to the Administration Portal to confirm that the warning no longer appears.

If you previously imported a CA or https certificate into the browser, find the certificate(s), remove them from the browser, and reimport the new CA certificate. Install the certificate authority according to the instructions provided by your browser. To get the certificate authority’s certificate, navigate to http://your-manager-fqdn/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA, replacing your-manager-fqdn with the fully qualified domain name (FQDN).

Log in to the Engine machine as the root user.

Check whether /etc/pki/ovirt-engine/openssl.conf includes the line default_md = sha256:

# cat /etc/pki/ovirt-engine/openssl.conf

# cp -p /etc/pki/ovirt-engine/openssl.conf /etc/pki/ovirt-engine/openssl.conf."$(date +"%Y%m%d%H%M%S")"
# sed -i 's/^default_md = sha1/default_md = sha256/' /etc/pki/ovirt-engine/openssl.conf

Re-sign the CA certificate by backing it up and creating a new certificate in ca.pem.new:

# cp -p /etc/pki/ovirt-engine/private/ca.pem /etc/pki/ovirt-engine/private/ca.pem."$(date +"%Y%m%d%H%M%S")"
# openssl x509 -signkey /etc/pki/ovirt-engine/private/ca.pem -in /etc/pki/ovirt-engine/ca.pem -out /etc/pki/ovirt-engine/ca.pem.new -days 3650 -sha256

Replace the existing certificate with the new certificate:

# mv /etc/pki/ovirt-engine/ca.pem.new /etc/pki/ovirt-engine/ca.pem

Define the certificates that should be re-signed:

# names="engine apache websocket-proxy jboss imageio-proxy"

# names="engine websocket-proxy jboss imageio-proxy"

On the Engine, save a backup of the /etc/ovirt-engine/engine.conf.d and /etc/pki/ovirt-engine directories, and re-sign the certificates:

# . /etc/ovirt-engine/engine.conf.d/10-setup-protocols.conf
# for name in $names; do
    subject="$(
        openssl \
            x509 \
            -in /etc/pki/ovirt-engine/certs/"${name}".cer \
            -noout \
            -subject \
            -nameopt compat \
        | sed \
            's;subject=\(.*\);\1;' \
    )"
   /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
        --name="${name}" \
        --password=mypass \ <1>
        --subject="${subject}" \
        --san=DNS:"${ENGINE_FQDN}" \
        --keep-key
done

Restart the following services:

# systemctl restart httpd
# systemctl restart ovirt-engine
# systemctl restart ovirt-websocket-proxy
# systemctl restart ovirt-imageio

Connect to the Administration Portal to confirm that the warning no longer appears.

If you previously imported a CA or https certificate into the browser, find the certificate(s), remove them from the browser, and reimport the new CA certificate. Install the certificate authority according to the instructions provided by your browser. To get the certificate authority’s certificate, navigate to http://your-manager-fqdn/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA, replacing your-manager-fqdn with the fully qualified domain name (FQDN).

Enroll the certificates on the hosts. Repeat the following procedure for each host.

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

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

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

# hosted-engine --vm-status

On the Engine machine, check if updated packages are available:

# engine-upgrade-check

Update the setup packages:

# dnf update ovirt\*setup\*

Update the oVirt Engine 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

Execution of setup completed successfully

Update the base operating system and any optional packages installed on the Engine:

# yum update --nobest

Enable oVirt 4.5 repositories

# dnf install -y centos-release-ovirt45

Enable oVirt 4.5 repositories

Enable oVirt 4.5 repositories

Follow the procedure for updates between minor releases.

Follow the procedure for updating the cluster compatibility version.

In the Administration Portal, click Compute  Clusters.

Select the cluster to change and click Edit.

On the General tab, change the Compatibility Version to the desired value.

Click OK. The Change Cluster Compatibility Version confirmation dialog opens.

Click OK to confirm.

In the Administration Portal, click Compute  Virtual Machines.

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

next_run_config_exists=True

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

In the Administration Portal, click Compute  Data Centers.

Select the data center to change and click Edit.

Change the Compatibility Version to the desired value.

Click OK. The Change Data Center Compatibility Version confirmation dialog opens.

Click OK to confirm.

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

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

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

# hosted-engine --vm-status

On the Engine machine, check if updated packages are available:

# engine-upgrade-check

Update the setup packages:

# dnf update ovirt\*setup\*

Update the oVirt Engine 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

Execution of setup completed successfully

Update the base operating system and any optional packages installed on the Engine:

# yum update --nobest

Log in to the Engine virtual machine and shut down the engine service.

# systemctl stop ovirt-engine

Back up the oVirt Engine 4.3 environment.

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

Copy the backup file to a storage device outside of the oVirt environment.

Shut down the self-hosted engine.

# shutdown

Make sure that the self-hosted engine is shut down.

# hosted-engine --vm-status | grep -E 'Engine status|Hostname'

Install oVirt Node 4.4 or Enterprise Linux 8.6 on the existing node currently running the Engine virtual machine to use it as the self-hosted engine deployment host. See Installing the Self-hosted Engine Deployment Host for more information.

Install the self-hosted engine deployment tool.

# yum install ovirt-hosted-engine-setup

Copy the backup file to the host.

Log in to the Engine host and deploy the self-hosted engine with the backup file:

# hosted-engine --deploy --restore-from-file=/path/backup.bck

# tmux
# hosted-engine --deploy --restore-from-file=backup.bck

Detach the storage domain that hosts the Engine 4.3 machine. For details, see Detaching a Storage Domain from a Data Center in the Administration Guide.

Log in to the Engine virtual machine and shut down the engine service.

# systemctl stop ovirt-engine

Install optional extension packages if they were installed on the oVirt Engine 4.3 machine.

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

Configure the Engine by running the engine-setup command:

# engine-setup

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.

Put the host into maintenance mode and remove the host from the Engine. For more information, see Removing a Host in the Administration Guide.

Install Enterprise Linux 8.6, or oVirt Node 4.4. For more information, see Installing Hosts for oVirt in one of the Installing oVirt guides.

Install the appropriate packages to enable the host for oVirt 4.4. For more information, see Installing Hosts for oVirt in one of the Installing oVirt guides.

Add this host to the Engine, assigning it to the same cluster. You can now migrate virtual machines onto this host. For more information, see Adding Standard Hosts to the Engine in one of the Installing oVirt guides.

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

Reinstall the oVirt Node, as described in Installing oVirt Node in the Installation Guide.

# clearpart --all --drives=device

On the reinstalled host, create a directory, for example /data in which to recover the previous environment.

# mkdir /data

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

# mount /dev/sdX1 /data

Set the following permissions for the new directory.

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

oVirt 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

In the Administration Portal, create a data center and select Local in the Storage Type drop-down menu.

Configure a cluster on the new data center. See Creating a New Cluster in the Administration Guide for more information.

Add the host to the Engine. See Adding Standard Hosts to the oVirt Manager in one of the Installing oVirt guides for more information.

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

In the Administration Portal, open the Storage tab and click New Domain to create a new local storage domain.

Set the name to localfs and set the path to /localfs.

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.

Click OK to confirm the message that appears informing you that storage domains are already attached to the data center.

Activate the new storage domain:

Once the new storage domain is active, import the virtual machines and their disks:

Once you have ensured that all virtual machines have been successfully imported and are functioning properly, you can move localfs to maintenance mode.

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

In the Administration Portal, click Compute  Clusters.

Select the cluster to change and click Edit.

On the General tab, change the Compatibility Version to the desired value.

Click OK. The Change Cluster Compatibility Version confirmation dialog opens.

Click OK to confirm.

In the Administration Portal, click Compute  Virtual Machines.

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

next_run_config_exists=True

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

In the Administration Portal, click Compute  Data Centers.

Select the data center to change and click Edit.

Change the Compatibility Version to the desired value.

Click OK. The Change Data Center Compatibility Version confirmation dialog opens.

Click OK to confirm.

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

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

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

# hosted-engine --vm-status

On the Engine machine, check if updated packages are available:

# engine-upgrade-check

Update the setup packages:

# dnf update ovirt\*setup\*

Update the oVirt Engine 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

Execution of setup completed successfully

Update the base operating system and any optional packages installed on the Engine:

# yum update --nobest

Enable the oVirt 4.3 repositories:

# yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm

Update the setup packages:

# yum update ovirt\*setup\*

Run engine-setup and follow the prompts to upgrade the oVirt Engine:

# engine-setup

Execution of setup completed successfully

Update the base operating system:

# yum update

Log in to the Engine virtual machine and shut it down.

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

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

Confirm that the environment is running:

# hosted-engine --vm-status

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

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

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.

Click Upgrade.

Select the hosts to update, then click Next.

Configure the options:

Click Next.

Review the summary of the hosts and virtual machines that are affected.

Click Upgrade.

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.

In the Administration Portal, click Compute  Clusters.

Select the cluster to change and click Edit.

On the General tab, change the Compatibility Version to the desired value.

Click OK. The Change Cluster Compatibility Version confirmation dialog opens.

Click OK to confirm.

In the Administration Portal, click Compute  Virtual Machines.

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

next_run_config_exists=True

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

In the Administration Portal, click Compute  Data Centers.

Select the data center to change and click Edit.

Change the Compatibility Version to the desired value.

Click OK. The Change Data Center Compatibility Version confirmation dialog opens.

Click OK to confirm.

Log in to the Engine machine as the root user.

Check whether /etc/pki/ovirt-engine/openssl.conf includes the line default_md = sha256:

# cat /etc/pki/ovirt-engine/openssl.conf

# cp -p /etc/pki/ovirt-engine/openssl.conf /etc/pki/ovirt-engine/openssl.conf."$(date +"%Y%m%d%H%M%S")"
# sed -i 's/^default_md = sha1/default_md = sha256/' /etc/pki/ovirt-engine/openssl.conf

Define the certificate that should be re-signed:

# names="apache"

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

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

On the Engine, save a backup of the /etc/ovirt-engine/engine.conf.d and /etc/pki/ovirt-engine directories, and re-sign the certificates:

# . /etc/ovirt-engine/engine.conf.d/10-setup-protocols.conf
# for name in $names; do
    subject="$(
        openssl \
            x509 \
            -in /etc/pki/ovirt-engine/certs/"${name}".cer \
            -noout \
            -subject \
            -nameopt compat \
        | sed \
            's;subject=\(.*\);\1;' \
    )"
   /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
        --name="${name}" \
        --password=mypass \ <1>
        --subject="${subject}" \
        --san=DNS:"${ENGINE_FQDN}" \
        --keep-key
done

Restart the httpd service:

# systemctl restart httpd

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

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

Connect to the Administration Portal to confirm that the warning no longer appears.

If you previously imported a CA or https certificate into the browser, find the certificate(s), remove them from the browser, and reimport the new CA certificate. Install the certificate authority according to the instructions provided by your browser. To get the certificate authority’s certificate, navigate to http://your-manager-fqdn/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA, replacing your-manager-fqdn with the fully qualified domain name (FQDN).

Log in to the Engine machine as the root user.

Check whether /etc/pki/ovirt-engine/openssl.conf includes the line default_md = sha256:

# cat /etc/pki/ovirt-engine/openssl.conf

# cp -p /etc/pki/ovirt-engine/openssl.conf /etc/pki/ovirt-engine/openssl.conf."$(date +"%Y%m%d%H%M%S")"
# sed -i 's/^default_md = sha1/default_md = sha256/' /etc/pki/ovirt-engine/openssl.conf

Re-sign the CA certificate by backing it up and creating a new certificate in ca.pem.new:

# cp -p /etc/pki/ovirt-engine/private/ca.pem /etc/pki/ovirt-engine/private/ca.pem."$(date +"%Y%m%d%H%M%S")"
# openssl x509 -signkey /etc/pki/ovirt-engine/private/ca.pem -in /etc/pki/ovirt-engine/ca.pem -out /etc/pki/ovirt-engine/ca.pem.new -days 3650 -sha256

Replace the existing certificate with the new certificate:

# mv /etc/pki/ovirt-engine/ca.pem.new /etc/pki/ovirt-engine/ca.pem

Define the certificates that should be re-signed:

# names="engine apache websocket-proxy jboss imageio-proxy"

# names="engine websocket-proxy jboss imageio-proxy"

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

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

On the Engine, save a backup of the /etc/ovirt-engine/engine.conf.d and /etc/pki/ovirt-engine directories, and re-sign the certificates:

# . /etc/ovirt-engine/engine.conf.d/10-setup-protocols.conf
# for name in $names; do
    subject="$(
        openssl \
            x509 \
            -in /etc/pki/ovirt-engine/certs/"${name}".cer \
            -noout \
            -subject \
            -nameopt compat \
        | sed \
            's;subject=\(.*\);\1;' \
    )"
   /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
        --name="${name}" \
        --password=mypass \ <1>
        --subject="${subject}" \
        --san=DNS:"${ENGINE_FQDN}" \
        --keep-key
done

Restart the following services:

# systemctl restart httpd
# systemctl restart ovirt-engine
# systemctl restart ovirt-websocket-proxy
# systemctl restart ovirt-imageio

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

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

Connect to the Administration Portal to confirm that the warning no longer appears.

If you previously imported a CA or https certificate into the browser, find the certificate(s), remove them from the browser, and reimport the new CA certificate. Install the certificate authority according to the instructions provided by your browser. To get the certificate authority’s certificate, navigate to http://your-manager-fqdn/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA, replacing your-manager-fqdn with the fully qualified domain name (FQDN).

Enroll the certificates on the hosts. Repeat the following procedure for each host.

On the Engine machine, check if updated packages are available:

# engine-upgrade-check

Update the setup packages:

# dnf update ovirt\*setup\*

Update the oVirt Engine 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

Execution of setup completed successfully

Update the base operating system and any optional packages installed on the Engine:

# yum update --nobest

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

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

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

# hosted-engine --vm-status

On the Engine machine, check if updated packages are available:

# engine-upgrade-check

Update the setup packages:

# dnf update ovirt\*setup\*

Update the oVirt Engine 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

Execution of setup completed successfully

Update the base operating system and any optional packages installed on the Engine:

# yum update --nobest

Log in to the Engine virtual machine and shut it down.

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

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

Confirm that the environment is running:

# hosted-engine --vm-status

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

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

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.

Click Upgrade.

Select the hosts to update, then click Next.

Configure the options:

Click Next.

Review the summary of the hosts and virtual machines that are affected.

Click Upgrade.

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.

In the Administration Portal, click Compute  Clusters.

Select the cluster to change and click Edit.

On the General tab, change the Compatibility Version to the desired value.

Click OK. The Change Cluster Compatibility Version confirmation dialog opens.

Click OK to confirm.

In the Administration Portal, click Compute  Virtual Machines.

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

next_run_config_exists=True

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

In the Administration Portal, click Compute  Data Centers.

Select the data center to change and click Edit.

Change the Compatibility Version to the desired value.

Click OK. The Change Data Center Compatibility Version confirmation dialog opens.

Click OK to confirm.

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

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

Click Installation  Check for Upgrade and click OK.

If an update is available, click Installation  Upgrade.

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.

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

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

Click Management  Maintenance and OK.

For Enterprise Linux hosts:

Enable version 14 of the nodejs module:

# dnf module -y enable nodejs:14

Update the host:

# dnf upgrade --nobest

Reboot the host to ensure all updates are correctly applied.