Procedure

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

   # engine-upgrade-check

2. Update the setup packages:

   # yum update rhevm-setup

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

   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 may 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 may take some time; allow time for the update process to complete and do not stop the process once initiated.

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

   # yum update

   Important

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

Procedure

1. On the 3.6 Manager, back up the environment:

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

2. Copy the backup file to a suitable device or machine.

3. If the ISO storage domain is hosted on the Manager machine, back up the contents of /var/lib/exports/iso:

   # cd /var/lib/exports/iso
   # tar zcf iso_domain.tar.gz UUID

   You will restore the ISO storage backup file after the upgrade.

4. Install Red Hat Enterprise Linux 7. See the Red Hat Enterprise Linux Installation Guide.

   If you are installing RHEL 7 on a new machine, you must configure it to have the same fully qualified domain name as the 3.6 Manager machine, and update your DNS so that the FQDN correlates to the IP address of the new machine.

5. Install the Red Hat Virtualization 4.0 packages:

   1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:

      # subscription-manager register

   2. Find the Red Hat Enterprise Linux Server and Red Hat Virtualization subscription pools and record the pool IDs:

      # subscription-manager list --available

   3. Use the pool IDs to attach the entitlements to the system:

      # subscription-manager attach --pool=pool_id

   4. Configure the repositories:

      # subscription-manager repos \
          --enable=rhel-7-server-rpms \
          --enable=rhel-7-server-supplementary-rpms \
          --enable=rhel-7-server-rhv-4.0-rpms \
          --enable=jb-eap-7.0-for-rhel-7-server-rpms

   5. Ensure all packages are up to date:

      # yum update

   6. Install the rhevm package and dependencies:

      # yum install rhevm

6. Copy the backup file to the 4.0 Manager machine and restore the backup:

   # engine-backup --mode=restore --file=backup.bck --log=restore.log \
       --provision-db --provision-dwh-db --restore-permissions

   Note

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

   Note

   Use the --provision-dwh-db option if the backup contains Data Warehouse data.

   Red Hat Enterprise Virtualization Reports has been deprecated in Red Hat Virtualization 4.0 and will not be restored. See BZ#1340810 for more information.

7. Install optional extension packages if they were installed on the 3.6 Manager machine:

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

   Note

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

8. Decommission the 3.6 Manager machine if you are using a different machine for the 4.0 Manager.

9. Run engine-setup to configure the Manager:

   # engine-setup

Procedure

1. Enable the Red Hat Virtualization 4.1 repositories:

   # subscription-manager repos \
       --enable=rhel-7-server-rhv-4.1-rpms \
       --enable=rhel-7-server-rhv-4-tools-rpms \
       --enable=jb-eap-7.1-for-rhel-7-server-rpms

   All other repositories remain the same across Red Hat Virtualization releases.

2. Update the setup packages:

   # yum update ovirt\*setup\*

3. Run engine-setup and follow the prompts to upgrade the Red Hat Virtualization Manager:

   # engine-setup

4. Disable the Red Hat Virtualization 4.0 repositories to ensure the system does not use any 4.0 packages:

   # subscription-manager repos \
       --disable=rhel-7-server-rhv-4.0-rpms \
       --disable=jb-eap-7-for-rhel-7-server-rpms \
       --disable=jb-eap-7.0-for-rhel-7-server-rpms

5. Update the base operating system:

   # yum update

6. Reboot the machine.

Procedure

1. Enable the Red Hat Virtualization 4.2 repositories:

   # subscription-manager repos \
       --enable=rhel-7-server-rhv-4.2-manager-rpms \
       --enable=rhel-7-server-rhv-4-manager-tools-rpms \
       --enable=jb-eap-7-for-rhel-7-server-rpms \
       --enable=rhel-7-server-ansible-2.9-rpms

   All other repositories remain the same across Red Hat Virtualization releases.

2. Update the setup packages:

   # yum update ovirt\*setup\*

3. Run engine-setup and follow the prompts to upgrade the Red Hat Virtualization Manager:

   # engine-setup

   Note

   If you changed the default trust keystore password, you might get a keystore certificate error. If so, update the configuration to reflect the correct password. For more information, see RHV 4.2 - Failed to import provider certificate into the external provider keystore

4. Disable the Red Hat Virtualization 4.1 repositories to ensure the system does not use any 4.1 packages:

   # subscription-manager repos \
       --disable=rhel-7-server-rhv-4.1-rpms \
       --disable=rhel-7-server-rhv-4.1-manager-rpms \
       --disable=rhel-7-server-rhv-4-tools-rpms \
       --disable=jb-eap-7.0-for-rhel-7-server-rpms \
       --disable=jb-eap-7.1-for-rhel-7-server-rpms

5. Update the base operating system:

   # yum update

6. Reboot the machine.

Procedure

1. If your Red Hat Enterprise Linux hosts are locked to version 7.3, as described in https://access.redhat.com/solutions/3194482, set them to the general RHEL 7 version before updating (to view the version number, type subscription-manager release --show):

   # subscription-manager release --set=7Server

2. Disable your current repositories:

   # subscription-manager repos --disable='*'

3. Ensure that the correct repositories are enabled (to view a list of currently enabled repositories, type yum repolist):

   • For Red Hat Virtualization Hosts:

     # subscription-manager repos --enable=rhel-7-server-rhvh-4-rpms

   • For Red Hat Enterprise Linux hosts:

     # subscription-manager repos \
         --enable=rhel-7-server-rpms \
         --enable=rhel-7-server-rhv-4-mgmt-agent-rpms \
         --enable=rhel-7-server-ansible-2.9-rpms

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

5. Click Installation → Check for Upgrade and click OK.

   Click the Events and alerts notification icon ( ) and expand the Events section to see the result.

6. If an update is available, click Installation → Upgrade.

7. Click OK to update the host. Running virtual machines will be migrated according to their migration policy. If migration is disabled for any virtual machines, you will be 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

     If any virtual machines were migrated off the host, they are now migrated back.

     Note

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

Procedure

1. Click Compute → Clusters and select the cluster to change.
2. Click Edit.
3. Change the Compatibility Version to the desired value.
4. Click OK to open the Change Cluster Compatibility Version confirmation window.
5. Click OK to confirm.

Procedure

1. Click Compute → Data Centers and select the data center to change.
2. Click Edit.
3. Change the Compatibility Version to the desired value.
4. Click OK to open the Change Data Center Compatibility Version confirmation window.
5. Click OK to confirm.

1. Create an export directory on the storage server and set its permissions:

   # mkdir -p /var/lib/exports/iso
   # chown -R 36:36 /var/lib/exports/

2. Extract the ISO domain backup to this directory:

   # cd /var/lib/exports/iso
   # tar zxf iso_domain.tar.gz

3. Set the SELinux context for the files in the export directory:

   # chcon -R system_u:object_r:public_content_rw_t:s0 /var/lib/exports/iso/

4. Create /etc/exports.d/ovirt-engine-iso-domain.exports with the following line:

   /var/lib/exports/iso  *(rw)

5. Edit the following lines in /etc/sysconfig/nfs:

   RPCMOUNTDOPTS="-p 892"
   (..snip..)
   STATDARGS="-p 662 -o 2020"
   (..snip..)
   LOCKD_UDPPORT=32769
   LOCKD_TCPPORT=32803
   RPCRQUOTAOPTS="-p 875"

6. Enable the nfs service:

   # systemctl enable nfs
   # systemctl start nfs

7. Allow services and ports with firewalld:

   # firewall-cmd --add-service={nfs,rpc-bind}
   # firewall-cmd --add-service={nfs,rpc-bind} --permanent
   # firewall-cmd --add-port={32769/udp,32803/tcp,662/tcp,662/udp,875/tcp,875/udp,892/tcp,892/udp}
   # firewall-cmd --add-port={32769/udp,32803/tcp,662/tcp,662/udp,875/tcp,875/udp,892/tcp,892/udp} --permanent

8. In the Administration Portal, update the ISO domain’s storage path:

   1. Click Storage → Domains.
   2. Click the ISO domain’s name to go to the details view.
   3. Click the Data Center tab and click Maintenance.
   4. When the ISO domain is in maintenance mode, click Manage Domain.
   5. Change the Export Path to point to the new directory, for example: storage.example.com:/var/lib/exports/iso
   6. Click OK.

1. Log in to the Manager machine as the root user.

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

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

   If it still includes default_md = sha1, back up the existing configuration and change the default to sha256:

   # 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

3. Define the certificate that should be re-signed:

   # names="apache"

4. On the Manager, re-sign the Apache certificate:

   for name in $names; do
       subject="$(
           openssl \
               x509 \
               -in /etc/pki/ovirt-engine/certs/"${name}".cer \
               -noout \
               -subject \
           | sed \
               's;subject= \(.*\);\1;' \
       )"
      /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
           --name="${name}" \
           --password=mypass \
           --subject="${subject}" \
           --keep-key
   done

5. Restart the httpd service:

   # systemctl restart httpd

6. Connect to the Administration Portal to confirm that the warning no longer appears.
7. 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).

1. Log in to the Manager machine as the root user.

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

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

   If it still includes default_md = sha1, back up the existing configuration and change the default to sha256:

   # 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

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

4. Replace the existing certificate with the new certificate:

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

5. Define the certificates that should be re-signed:

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

   If you replaced the Red Hat Virtualization Manager SSL Certificate after the upgrade, run the following instead:

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

   For more details see Replacing the Red Hat Virtualization Manager SSL Certificate in the Administration Guide.

6. On the Manager, re-sign the certificates:

   for name in $names; do
      subject="$(
           openssl \
               x509 \
               -in /etc/pki/ovirt-engine/certs/"${name}".cer \
               -noout \
               -subject \
           | sed \
               's;subject= \(.*\);\1;' \
           )"
        /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
               --name="${name}" \
               --password=mypass \
               --subject="${subject}" \
               --keep-key
   done

7. Restart the following services:

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

8. Connect to the Administration Portal to confirm that the warning no longer appears.
9. 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).

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

    1. In the Administration Portal, click Compute → Hosts.
    2. Select the host and click Management → Maintenance.
    3. Once the host is in maintenance mode, click Installation → Enroll Certificate.
    4. Click Management → Activate.

Procedure

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

   # engine-upgrade-check

2. Update the setup packages:

   # yum update ovirt\*setup\*

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

   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 may 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 may take some time; allow time for the update process to complete and do not stop the process once initiated.

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

   # yum update

   Important

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

Procedure

1. Enable the Red Hat Virtualization 4.1 repositories:

   # subscription-manager repos \
       --enable=rhel-7-server-rhv-4.1-rpms \
       --enable=rhel-7-server-rhv-4-tools-rpms \
       --enable=jb-eap-7.1-for-rhel-7-server-rpms

   All other repositories remain the same across Red Hat Virtualization releases.

2. Update the setup packages:

   # yum update ovirt\*setup\*

3. Run engine-setup and follow the prompts to upgrade the Red Hat Virtualization Manager:

   # engine-setup

4. Disable the Red Hat Virtualization 4.0 repositories to ensure the system does not use any 4.0 packages:

   # subscription-manager repos \
       --disable=rhel-7-server-rhv-4.0-rpms \
       --disable=jb-eap-7-for-rhel-7-server-rpms \
       --disable=jb-eap-7.0-for-rhel-7-server-rpms

5. Update the base operating system:

   # yum update

6. Reboot the machine.

Procedure

1. Enable the Red Hat Virtualization 4.2 repositories:

   # subscription-manager repos \
       --enable=rhel-7-server-rhv-4.2-manager-rpms \
       --enable=rhel-7-server-rhv-4-manager-tools-rpms \
       --enable=jb-eap-7-for-rhel-7-server-rpms \
       --enable=rhel-7-server-ansible-2.9-rpms

   All other repositories remain the same across Red Hat Virtualization releases.

2. Update the setup packages:

   # yum update ovirt\*setup\*

3. Run engine-setup and follow the prompts to upgrade the Red Hat Virtualization Manager:

   # engine-setup

   Note

   If you changed the default trust keystore password, you might get a keystore certificate error. If so, update the configuration to reflect the correct password. For more information, see RHV 4.2 - Failed to import provider certificate into the external provider keystore

4. Disable the Red Hat Virtualization 4.1 repositories to ensure the system does not use any 4.1 packages:

   # subscription-manager repos \
       --disable=rhel-7-server-rhv-4.1-rpms \
       --disable=rhel-7-server-rhv-4.1-manager-rpms \
       --disable=rhel-7-server-rhv-4-tools-rpms \
       --disable=jb-eap-7.0-for-rhel-7-server-rpms \
       --disable=jb-eap-7.1-for-rhel-7-server-rpms

5. Update the base operating system:

   # yum update

6. Reboot the machine.

Procedure

1. Ensure that the correct repositories are enabled (to view a list of currently enabled repositories, type yum repolist):

   • For Red Hat Virtualization Hosts:

     # subscription-manager repos --enable=rhel-7-server-rhvh-4-rpms

   • For Red Hat Enterprise Linux hosts:

     # subscription-manager repos \
         --enable=rhel-7-server-rpms \
         --enable=rhel-7-server-rhv-4-mgmt-agent-rpms \
         --enable=rhel-7-server-ansible-2.9-rpms

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

3. Click Installation → Check for Upgrade and click OK.

   Click the Events and alerts notification icon ( ) 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 will be migrated according to their migration policy. If migration is disabled for any virtual machines, you will be 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

     If any virtual machines were migrated off the host, they are now migrated back.

     Note

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

Procedure

1. Click Compute → Clusters and select the cluster to change.
2. Click Edit.
3. Change the Compatibility Version to the desired value.
4. Click OK to open the Change Cluster Compatibility Version confirmation window.
5. Click OK to confirm.

Procedure

1. Click Compute → Data Centers and select the data center to change.
2. Click Edit.
3. Change the Compatibility Version to the desired value.
4. Click OK to open the Change Data Center Compatibility Version confirmation window.
5. Click OK to confirm.

1. Log in to the Manager machine as the root user.

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

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

   If it still includes default_md = sha1, back up the existing configuration and change the default to sha256:

   # 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

3. Define the certificate that should be re-signed:

   # names="apache"

4. On the Manager, re-sign the Apache certificate:

   for name in $names; do
       subject="$(
           openssl \
               x509 \
               -in /etc/pki/ovirt-engine/certs/"${name}".cer \
               -noout \
               -subject \
           | sed \
               's;subject= \(.*\);\1;' \
       )"
      /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
           --name="${name}" \
           --password=mypass \
           --subject="${subject}" \
           --keep-key
   done

5. Restart the httpd service:

   # systemctl restart httpd

6. Connect to the Administration Portal to confirm that the warning no longer appears.
7. 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).

1. Log in to the Manager machine as the root user.

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

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

   If it still includes default_md = sha1, back up the existing configuration and change the default to sha256:

   # 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

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

4. Replace the existing certificate with the new certificate:

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

5. Define the certificates that should be re-signed:

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

   If you replaced the Red Hat Virtualization Manager SSL Certificate after the upgrade, run the following instead:

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

   For more details see Replacing the Red Hat Virtualization Manager SSL Certificate in the Administration Guide.

6. On the Manager, re-sign the certificates:

   for name in $names; do
      subject="$(
           openssl \
               x509 \
               -in /etc/pki/ovirt-engine/certs/"${name}".cer \
               -noout \
               -subject \
           | sed \
               's;subject= \(.*\);\1;' \
           )"
        /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
               --name="${name}" \
               --password=mypass \
               --subject="${subject}" \
               --keep-key
   done

7. Restart the following services:

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

8. Connect to the Administration Portal to confirm that the warning no longer appears.
9. 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).

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

    1. In the Administration Portal, click Compute → Hosts.
    2. Select the host and click Management → Maintenance.
    3. Once the host is in maintenance mode, click Installation → Enroll Certificate.
    4. Click Management → Activate.

Procedure

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

   # engine-upgrade-check

2. Update the setup packages:

   # yum update ovirt\*setup\*

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

   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 may 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 may take some time; allow time for the update process to complete and do not stop the process once initiated.

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

   # yum update

   Important

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

Procedure

1. Enable the Red Hat Virtualization 4.2 repositories:

   # subscription-manager repos \
       --enable=rhel-7-server-rhv-4.2-manager-rpms \
       --enable=rhel-7-server-rhv-4-manager-tools-rpms \
       --enable=jb-eap-7-for-rhel-7-server-rpms \
       --enable=rhel-7-server-ansible-2.9-rpms

   All other repositories remain the same across Red Hat Virtualization releases.

2. Update the setup packages:

   # yum update ovirt\*setup\*

3. Run engine-setup and follow the prompts to upgrade the Red Hat Virtualization Manager:

   # engine-setup

   Note

   If you changed the default trust keystore password, you might get a keystore certificate error. If so, update the configuration to reflect the correct password. For more information, see RHV 4.2 - Failed to import provider certificate into the external provider keystore

4. Disable the Red Hat Virtualization 4.1 repositories to ensure the system does not use any 4.1 packages:

   # subscription-manager repos \
       --disable=rhel-7-server-rhv-4.1-rpms \
       --disable=rhel-7-server-rhv-4.1-manager-rpms \
       --disable=rhel-7-server-rhv-4-tools-rpms \
       --disable=jb-eap-7.0-for-rhel-7-server-rpms \
       --disable=jb-eap-7.1-for-rhel-7-server-rpms

5. Update the base operating system:

   # yum update

6. Reboot the machine.

Procedure

1. Ensure that the correct repositories are enabled (to view a list of currently enabled repositories, type yum repolist):

   • For Red Hat Virtualization Hosts:

     # subscription-manager repos --enable=rhel-7-server-rhvh-4-rpms

   • For Red Hat Enterprise Linux hosts:

     # subscription-manager repos \
         --enable=rhel-7-server-rpms \
         --enable=rhel-7-server-rhv-4-mgmt-agent-rpms \
         --enable=rhel-7-server-ansible-2.9-rpms

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

3. Click Installation → Check for Upgrade and click OK.

   Click the Events and alerts notification icon ( ) 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 will be migrated according to their migration policy. If migration is disabled for any virtual machines, you will be 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

     If any virtual machines were migrated off the host, they are now migrated back.

     Note

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

Procedure

1. Click Compute → Clusters and select the cluster to change.
2. Click Edit.
3. Change the Compatibility Version to the desired value.
4. Click OK to open the Change Cluster Compatibility Version confirmation window.
5. Click OK to confirm.

Procedure

1. Click Compute → Data Centers and select the data center to change.
2. Click Edit.
3. Change the Compatibility Version to the desired value.
4. Click OK to open the Change Data Center Compatibility Version confirmation window.
5. Click OK to confirm.

1. Log in to the Manager machine as the root user.

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

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

   If it still includes default_md = sha1, back up the existing configuration and change the default to sha256:

   # 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

3. Define the certificate that should be re-signed:

   # names="apache"

4. On the Manager, re-sign the Apache certificate:

   for name in $names; do
       subject="$(
           openssl \
               x509 \
               -in /etc/pki/ovirt-engine/certs/"${name}".cer \
               -noout \
               -subject \
           | sed \
               's;subject= \(.*\);\1;' \
       )"
      /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
           --name="${name}" \
           --password=mypass \
           --subject="${subject}" \
           --keep-key
   done

5. Restart the httpd service:

   # systemctl restart httpd

6. Connect to the Administration Portal to confirm that the warning no longer appears.
7. 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).

1. Log in to the Manager machine as the root user.

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

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

   If it still includes default_md = sha1, back up the existing configuration and change the default to sha256:

   # 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

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

4. Replace the existing certificate with the new certificate:

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

5. Define the certificates that should be re-signed:

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

   If you replaced the Red Hat Virtualization Manager SSL Certificate after the upgrade, run the following instead:

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

   For more details see Replacing the Red Hat Virtualization Manager SSL Certificate in the Administration Guide.

6. On the Manager, re-sign the certificates:

   for name in $names; do
      subject="$(
           openssl \
               x509 \
               -in /etc/pki/ovirt-engine/certs/"${name}".cer \
               -noout \
               -subject \
           | sed \
               's;subject= \(.*\);\1;' \
           )"
        /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
               --name="${name}" \
               --password=mypass \
               --subject="${subject}" \
               --keep-key
   done

7. Restart the following services:

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

8. Connect to the Administration Portal to confirm that the warning no longer appears.
9. 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).

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

    1. In the Administration Portal, click Compute → Hosts.
    2. Select the host and click Management → Maintenance.
    3. Once the host is in maintenance mode, click Installation → Enroll Certificate.
    4. Click Management → Activate.

Procedure

1. Click Administration → Providers and select the OVN provider.
2. Click Edit.
3. Click the Networking Plugin text field and select oVirt Network Provider for OVN from the drop-down list.
4. Click OK.

Procedure

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

   # engine-upgrade-check

2. Update the setup packages:

   # yum update rhevm-setup

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

   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 may 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 may take some time; allow time for the update process to complete and do not stop the process once initiated.

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

   # yum update

   Important

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

Procedure

1. On the 3.6 Manager, back up the environment:

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

2. Copy the backup file to a suitable device or machine.

3. If the ISO storage domain is hosted on the Manager machine, back up the contents of /var/lib/exports/iso:

   # cd /var/lib/exports/iso
   # tar zcf iso_domain.tar.gz UUID

   You will restore the ISO storage backup file after the upgrade.

4. Install Red Hat Enterprise Linux 7. See the Red Hat Enterprise Linux Installation Guide.

   If you are installing RHEL 7 on a new machine, you must configure it to have the same fully qualified domain name as the 3.6 Manager machine, and update your DNS so that the FQDN correlates to the IP address of the new machine.

5. Install the Red Hat Virtualization 4.0 packages:

   1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:

      # subscription-manager register

   2. Find the Red Hat Enterprise Linux Server and Red Hat Virtualization subscription pools and record the pool IDs:

      # subscription-manager list --available

   3. Use the pool IDs to attach the entitlements to the system:

      # subscription-manager attach --pool=pool_id

   4. Configure the repositories:

      # subscription-manager repos \
          --enable=rhel-7-server-rpms \
          --enable=rhel-7-server-supplementary-rpms \
          --enable=rhel-7-server-rhv-4.0-rpms \
          --enable=jb-eap-7.0-for-rhel-7-server-rpms

   5. Ensure all packages are up to date:

      # yum update

   6. Install the rhevm package and dependencies:

      # yum install rhevm

6. Copy the backup file to the 4.0 Manager machine and restore the backup:

   # engine-backup --mode=restore --file=backup.bck --log=restore.log \
       --provision-db --provision-dwh-db --restore-permissions

   Note

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

   Note

   Use the --provision-dwh-db option if the backup contains Data Warehouse data.

   Red Hat Enterprise Virtualization Reports has been deprecated in Red Hat Virtualization 4.0 and will not be restored. See BZ#1340810 for more information.

7. Install optional extension packages if they were installed on the 3.6 Manager machine:

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

   Note

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

8. Decommission the 3.6 Manager machine if you are using a different machine for the 4.0 Manager.

9. Run engine-setup to configure the Manager:

   # engine-setup

Procedure

1. Enable the Red Hat Virtualization 4.1 repositories:

   # subscription-manager repos \
       --enable=rhel-7-server-rhv-4.1-rpms \
       --enable=rhel-7-server-rhv-4-tools-rpms \
       --enable=jb-eap-7.1-for-rhel-7-server-rpms

   All other repositories remain the same across Red Hat Virtualization releases.

2. Update the setup packages:

   # yum update ovirt\*setup\*

3. Run engine-setup and follow the prompts to upgrade the Red Hat Virtualization Manager:

   # engine-setup

4. Disable the Red Hat Virtualization 4.0 repositories to ensure the system does not use any 4.0 packages:

   # subscription-manager repos \
       --disable=rhel-7-server-rhv-4.0-rpms \
       --disable=jb-eap-7-for-rhel-7-server-rpms \
       --disable=jb-eap-7.0-for-rhel-7-server-rpms

5. Update the base operating system:

   # yum update

6. Reboot the machine.

1. Stop the service running on the machine:

   • Stop the ovirt-engine service on the Manager machine:

     # systemctl stop ovirt-engine

   • Stop the ovirt-engine-dwh service on the Data Warehouse machine:

     # systemctl stop ovirt-engine-dwhd

2. Enable the required repository to receive the PostgreSQL 9.5 package:

   Enable either the Red Hat Virtualization Manager repository:

   # subscription-manager repos --enable=rhel-7-server-rhv-4.2-manager-rpms

   or the SCL repository:

   # subscription-manager repos --enable rhel-server-rhscl-7-rpms

3. Install the PostgreSQL 9.5 packages:

   # yum install rh-postgresql95 rh-postgresql95-postgresql-contrib

4. Stop and disable the PostgreSQL 9.2 service:

   # systemctl stop postgresql
   # systemctl disable postgresql

5. Upgrade the PostgreSQL 9.2 database to PostgreSQL 9.5:

   # scl enable rh-postgresql95 -- postgresql-setup upgrade

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

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

   Ensure that you see an output similar to the following:

   rh-postgresql95-postgresql.service - PostgreSQL database server
      Loaded: loaded (/usr/lib/systemd/system/rh-postgresql95-postgresql.service;
   enabled; vendor preset: disabled)
      Active: active (running) since Mon 2018-05-07 08:48:27 CEST; 1h 59min ago

7. Log in to the database and enable the uuid-ossp extension:

   # su - postgres -c "scl enable rh-postgresql95 -- psql -d database-name"

8. Execute the following SQL commands:

   # database-name=# DROP FUNCTION IF EXISTS uuid_generate_v1();
   # database-name=# CREATE EXTENSION "uuid-ossp";

9. Copy the pg_hba.conf client configuration file from the 9.2 environment to your 9.5 environment:

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

10. Update the following parameters in the postgresql.conf file:

    # vi /var/opt/rh/rh-postgresql95/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'

11. Restart the PostgreSQL 9.5 service to apply the configuration changes:

    # systemctl restart rh-postgresql95-postgresql.service

    The remote databases have been upgraded.

Procedure

1. Enable the Red Hat Virtualization 4.2 repositories:

   # subscription-manager repos \
       --enable=rhel-7-server-rhv-4.2-manager-rpms \
       --enable=rhel-7-server-rhv-4-manager-tools-rpms \
       --enable=jb-eap-7-for-rhel-7-server-rpms \
       --enable=rhel-7-server-ansible-2.9-rpms

   All other repositories remain the same across Red Hat Virtualization releases.

2. Update the setup packages:

   # yum update ovirt\*setup\*

3. Run engine-setup and follow the prompts to upgrade the Red Hat Virtualization Manager:

   # engine-setup

   Note

   If you changed the default trust keystore password, you might get a keystore certificate error. If so, update the configuration to reflect the correct password. For more information, see RHV 4.2 - Failed to import provider certificate into the external provider keystore

4. Disable the Red Hat Virtualization 4.1 repositories to ensure the system does not use any 4.1 packages:

   # subscription-manager repos \
       --disable=rhel-7-server-rhv-4.1-rpms \
       --disable=rhel-7-server-rhv-4.1-manager-rpms \
       --disable=rhel-7-server-rhv-4-tools-rpms \
       --disable=jb-eap-7.0-for-rhel-7-server-rpms \
       --disable=jb-eap-7.1-for-rhel-7-server-rpms

5. Update the base operating system:

   # yum update

6. Reboot the machine.

7. If Data Warehouse is installed on a separate machine, log in to that machine and restart the ovirt-engine-dwhd service:

   # systemctl restart ovirt-engine-dwhd

Procedure

1. If your Red Hat Enterprise Linux hosts are locked to version 7.3, as described in https://access.redhat.com/solutions/3194482, set them to the general RHEL 7 version before updating (to view the version number, type subscription-manager release --show):

   # subscription-manager release --set=7Server

2. Disable your current repositories:

   # subscription-manager repos --disable='*'

3. Ensure that the correct repositories are enabled (to view a list of currently enabled repositories, type yum repolist):

   • For Red Hat Virtualization Hosts:

     # subscription-manager repos --enable=rhel-7-server-rhvh-4-rpms

   • For Red Hat Enterprise Linux hosts:

     # subscription-manager repos \
         --enable=rhel-7-server-rpms \
         --enable=rhel-7-server-rhv-4-mgmt-agent-rpms \
         --enable=rhel-7-server-ansible-2.9-rpms

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

5. Click Installation → Check for Upgrade and click OK.

   Click the Events and alerts notification icon ( ) and expand the Events section to see the result.

6. If an update is available, click Installation → Upgrade.

7. Click OK to update the host. Running virtual machines will be migrated according to their migration policy. If migration is disabled for any virtual machines, you will be 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

     If any virtual machines were migrated off the host, they are now migrated back.

     Note

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

Procedure

1. Click Compute → Clusters and select the cluster to change.
2. Click Edit.
3. Change the Compatibility Version to the desired value.
4. Click OK to open the Change Cluster Compatibility Version confirmation window.
5. Click OK to confirm.

Procedure

1. Click Compute → Data Centers and select the data center to change.
2. Click Edit.
3. Change the Compatibility Version to the desired value.
4. Click OK to open the Change Data Center Compatibility Version confirmation window.
5. Click OK to confirm.

1. Create an export directory on the storage server and set its permissions:

   # mkdir -p /var/lib/exports/iso
   # chown -R 36:36 /var/lib/exports/

2. Extract the ISO domain backup to this directory:

   # cd /var/lib/exports/iso
   # tar zxf iso_domain.tar.gz

3. Set the SELinux context for the files in the export directory:

   # chcon -R system_u:object_r:public_content_rw_t:s0 /var/lib/exports/iso/

4. Create /etc/exports.d/ovirt-engine-iso-domain.exports with the following line:

   /var/lib/exports/iso  *(rw)

5. Edit the following lines in /etc/sysconfig/nfs:

   RPCMOUNTDOPTS="-p 892"
   (..snip..)
   STATDARGS="-p 662 -o 2020"
   (..snip..)
   LOCKD_UDPPORT=32769
   LOCKD_TCPPORT=32803
   RPCRQUOTAOPTS="-p 875"

6. Enable the nfs service:

   # systemctl enable nfs
   # systemctl start nfs

7. Allow services and ports with firewalld:

   # firewall-cmd --add-service={nfs,rpc-bind}
   # firewall-cmd --add-service={nfs,rpc-bind} --permanent
   # firewall-cmd --add-port={32769/udp,32803/tcp,662/tcp,662/udp,875/tcp,875/udp,892/tcp,892/udp}
   # firewall-cmd --add-port={32769/udp,32803/tcp,662/tcp,662/udp,875/tcp,875/udp,892/tcp,892/udp} --permanent

8. In the Administration Portal, update the ISO domain’s storage path:

   1. Click Storage → Domains.
   2. Click the ISO domain’s name to go to the details view.
   3. Click the Data Center tab and click Maintenance.
   4. When the ISO domain is in maintenance mode, click Manage Domain.
   5. Change the Export Path to point to the new directory, for example: storage.example.com:/var/lib/exports/iso
   6. Click OK.

1. Log in to the Manager machine as the root user.

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

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

   If it still includes default_md = sha1, back up the existing configuration and change the default to sha256:

   # 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

3. Define the certificate that should be re-signed:

   # names="apache"

4. On the Manager, re-sign the Apache certificate:

   for name in $names; do
       subject="$(
           openssl \
               x509 \
               -in /etc/pki/ovirt-engine/certs/"${name}".cer \
               -noout \
               -subject \
           | sed \
               's;subject= \(.*\);\1;' \
       )"
      /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
           --name="${name}" \
           --password=mypass \
           --subject="${subject}" \
           --keep-key
   done

5. Restart the httpd service:

   # systemctl restart httpd

6. Connect to the Administration Portal to confirm that the warning no longer appears.
7. 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).

1. Log in to the Manager machine as the root user.

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

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

   If it still includes default_md = sha1, back up the existing configuration and change the default to sha256:

   # 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

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

4. Replace the existing certificate with the new certificate:

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

5. Define the certificates that should be re-signed:

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

   If you replaced the Red Hat Virtualization Manager SSL Certificate after the upgrade, run the following instead:

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

   For more details see Replacing the Red Hat Virtualization Manager SSL Certificate in the Administration Guide.

6. On the Manager, re-sign the certificates:

   for name in $names; do
      subject="$(
           openssl \
               x509 \
               -in /etc/pki/ovirt-engine/certs/"${name}".cer \
               -noout \
               -subject \
           | sed \
               's;subject= \(.*\);\1;' \
           )"
        /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
               --name="${name}" \
               --password=mypass \
               --subject="${subject}" \
               --keep-key
   done

7. Restart the following services:

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

8. Connect to the Administration Portal to confirm that the warning no longer appears.
9. 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).

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

    1. In the Administration Portal, click Compute → Hosts.
    2. Select the host and click Management → Maintenance.
    3. Once the host is in maintenance mode, click Installation → Enroll Certificate.
    4. Click Management → Activate.

Procedure

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

   # engine-upgrade-check

2. Update the setup packages:

   # yum update ovirt\*setup\*

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

   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 may 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 may take some time; allow time for the update process to complete and do not stop the process once initiated.

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

   # yum update

   Important

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

Procedure

1. Enable the Red Hat Virtualization 4.1 repositories:

   # subscription-manager repos \
       --enable=rhel-7-server-rhv-4.1-rpms \
       --enable=rhel-7-server-rhv-4-tools-rpms \
       --enable=jb-eap-7.1-for-rhel-7-server-rpms

   All other repositories remain the same across Red Hat Virtualization releases.

2. Update the setup packages:

   # yum update ovirt\*setup\*

3. Run engine-setup and follow the prompts to upgrade the Red Hat Virtualization Manager:

   # engine-setup

4. Disable the Red Hat Virtualization 4.0 repositories to ensure the system does not use any 4.0 packages:

   # subscription-manager repos \
       --disable=rhel-7-server-rhv-4.0-rpms \
       --disable=jb-eap-7-for-rhel-7-server-rpms \
       --disable=jb-eap-7.0-for-rhel-7-server-rpms

5. Update the base operating system:

   # yum update

6. Reboot the machine.

1. Stop the service running on the machine:

   • Stop the ovirt-engine service on the Manager machine:

     # systemctl stop ovirt-engine

   • Stop the ovirt-engine-dwh service on the Data Warehouse machine:

     # systemctl stop ovirt-engine-dwhd

2. Enable the required repository to receive the PostgreSQL 9.5 package:

   Enable either the Red Hat Virtualization Manager repository:

   # subscription-manager repos --enable=rhel-7-server-rhv-4.2-manager-rpms

   or the SCL repository:

   # subscription-manager repos --enable rhel-server-rhscl-7-rpms

3. Install the PostgreSQL 9.5 packages:

   # yum install rh-postgresql95 rh-postgresql95-postgresql-contrib

4. Stop and disable the PostgreSQL 9.2 service:

   # systemctl stop postgresql
   # systemctl disable postgresql

5. Upgrade the PostgreSQL 9.2 database to PostgreSQL 9.5:

   # scl enable rh-postgresql95 -- postgresql-setup upgrade

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

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

   Ensure that you see an output similar to the following:

   rh-postgresql95-postgresql.service - PostgreSQL database server
      Loaded: loaded (/usr/lib/systemd/system/rh-postgresql95-postgresql.service;
   enabled; vendor preset: disabled)
      Active: active (running) since Mon 2018-05-07 08:48:27 CEST; 1h 59min ago

7. Log in to the database and enable the uuid-ossp extension:

   # su - postgres -c "scl enable rh-postgresql95 -- psql -d database-name"

8. Execute the following SQL commands:

   # database-name=# DROP FUNCTION IF EXISTS uuid_generate_v1();
   # database-name=# CREATE EXTENSION "uuid-ossp";

9. Copy the pg_hba.conf client configuration file from the 9.2 environment to your 9.5 environment:

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

10. Update the following parameters in the postgresql.conf file:

    # vi /var/opt/rh/rh-postgresql95/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'

11. Restart the PostgreSQL 9.5 service to apply the configuration changes:

    # systemctl restart rh-postgresql95-postgresql.service

    The remote databases have been upgraded.

Procedure

1. Enable the Red Hat Virtualization 4.2 repositories:

   # subscription-manager repos \
       --enable=rhel-7-server-rhv-4.2-manager-rpms \
       --enable=rhel-7-server-rhv-4-manager-tools-rpms \
       --enable=jb-eap-7-for-rhel-7-server-rpms \
       --enable=rhel-7-server-ansible-2.9-rpms

   All other repositories remain the same across Red Hat Virtualization releases.

2. Update the setup packages:

   # yum update ovirt\*setup\*

3. Run engine-setup and follow the prompts to upgrade the Red Hat Virtualization Manager:

   # engine-setup

   Note

   If you changed the default trust keystore password, you might get a keystore certificate error. If so, update the configuration to reflect the correct password. For more information, see RHV 4.2 - Failed to import provider certificate into the external provider keystore

4. Disable the Red Hat Virtualization 4.1 repositories to ensure the system does not use any 4.1 packages:

   # subscription-manager repos \
       --disable=rhel-7-server-rhv-4.1-rpms \
       --disable=rhel-7-server-rhv-4.1-manager-rpms \
       --disable=rhel-7-server-rhv-4-tools-rpms \
       --disable=jb-eap-7.0-for-rhel-7-server-rpms \
       --disable=jb-eap-7.1-for-rhel-7-server-rpms

5. Update the base operating system:

   # yum update

6. Reboot the machine.

7. If Data Warehouse is installed on a separate machine, log in to that machine and restart the ovirt-engine-dwhd service:

   # systemctl restart ovirt-engine-dwhd

Procedure

1. Ensure that the correct repositories are enabled (to view a list of currently enabled repositories, type yum repolist):

   • For Red Hat Virtualization Hosts:

     # subscription-manager repos --enable=rhel-7-server-rhvh-4-rpms

   • For Red Hat Enterprise Linux hosts:

     # subscription-manager repos \
         --enable=rhel-7-server-rpms \
         --enable=rhel-7-server-rhv-4-mgmt-agent-rpms \
         --enable=rhel-7-server-ansible-2.9-rpms

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

3. Click Installation → Check for Upgrade and click OK.

   Click the Events and alerts notification icon ( ) 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 will be migrated according to their migration policy. If migration is disabled for any virtual machines, you will be 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

     If any virtual machines were migrated off the host, they are now migrated back.

     Note

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

Procedure

1. Click Compute → Clusters and select the cluster to change.
2. Click Edit.
3. Change the Compatibility Version to the desired value.
4. Click OK to open the Change Cluster Compatibility Version confirmation window.
5. Click OK to confirm.

Procedure

1. Click Compute → Data Centers and select the data center to change.
2. Click Edit.
3. Change the Compatibility Version to the desired value.
4. Click OK to open the Change Data Center Compatibility Version confirmation window.
5. Click OK to confirm.

1. Log in to the Manager machine as the root user.

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

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

   If it still includes default_md = sha1, back up the existing configuration and change the default to sha256:

   # 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

3. Define the certificate that should be re-signed:

   # names="apache"

4. On the Manager, re-sign the Apache certificate:

   for name in $names; do
       subject="$(
           openssl \
               x509 \
               -in /etc/pki/ovirt-engine/certs/"${name}".cer \
               -noout \
               -subject \
           | sed \
               's;subject= \(.*\);\1;' \
       )"
      /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
           --name="${name}" \
           --password=mypass \
           --subject="${subject}" \
           --keep-key
   done

5. Restart the httpd service:

   # systemctl restart httpd

6. Connect to the Administration Portal to confirm that the warning no longer appears.
7. 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).

1. Log in to the Manager machine as the root user.

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

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

   If it still includes default_md = sha1, back up the existing configuration and change the default to sha256:

   # 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

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

4. Replace the existing certificate with the new certificate:

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

5. Define the certificates that should be re-signed:

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

   If you replaced the Red Hat Virtualization Manager SSL Certificate after the upgrade, run the following instead:

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

   For more details see Replacing the Red Hat Virtualization Manager SSL Certificate in the Administration Guide.

6. On the Manager, re-sign the certificates:

   for name in $names; do
      subject="$(
           openssl \
               x509 \
               -in /etc/pki/ovirt-engine/certs/"${name}".cer \
               -noout \
               -subject \
           | sed \
               's;subject= \(.*\);\1;' \
           )"
        /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
               --name="${name}" \
               --password=mypass \
               --subject="${subject}" \
               --keep-key
   done

7. Restart the following services:

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

8. Connect to the Administration Portal to confirm that the warning no longer appears.
9. 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).

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

    1. In the Administration Portal, click Compute → Hosts.
    2. Select the host and click Management → Maintenance.
    3. Once the host is in maintenance mode, click Installation → Enroll Certificate.
    4. Click Management → Activate.

1. Stop the service running on the machine:

   • Stop the ovirt-engine service on the Manager machine:

     # systemctl stop ovirt-engine

   • Stop the ovirt-engine-dwh service on the Data Warehouse machine:

     # systemctl stop ovirt-engine-dwhd

2. Enable the required repository to receive the PostgreSQL 9.5 package:

   Enable either the Red Hat Virtualization Manager repository:

   # subscription-manager repos --enable=rhel-7-server-rhv-4.2-manager-rpms

   or the SCL repository:

   # subscription-manager repos --enable rhel-server-rhscl-7-rpms

3. Install the PostgreSQL 9.5 packages:

   # yum install rh-postgresql95 rh-postgresql95-postgresql-contrib

4. Stop and disable the PostgreSQL 9.2 service:

   # systemctl stop postgresql
   # systemctl disable postgresql

5. Upgrade the PostgreSQL 9.2 database to PostgreSQL 9.5:

   # scl enable rh-postgresql95 -- postgresql-setup upgrade

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

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

   Ensure that you see an output similar to the following:

   rh-postgresql95-postgresql.service - PostgreSQL database server
      Loaded: loaded (/usr/lib/systemd/system/rh-postgresql95-postgresql.service;
   enabled; vendor preset: disabled)
      Active: active (running) since Mon 2018-05-07 08:48:27 CEST; 1h 59min ago

7. Log in to the database and enable the uuid-ossp extension:

   # su - postgres -c "scl enable rh-postgresql95 -- psql -d database-name"

8. Execute the following SQL commands:

   # database-name=# DROP FUNCTION IF EXISTS uuid_generate_v1();
   # database-name=# CREATE EXTENSION "uuid-ossp";

9. Copy the pg_hba.conf client configuration file from the 9.2 environment to your 9.5 environment:

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

10. Update the following parameters in the postgresql.conf file:

    # vi /var/opt/rh/rh-postgresql95/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'

11. Restart the PostgreSQL 9.5 service to apply the configuration changes:

    # systemctl restart rh-postgresql95-postgresql.service

    The remote databases have been upgraded.

Procedure

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

   # engine-upgrade-check

2. Update the setup packages:

   # yum update ovirt\*setup\*

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

   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 may 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 may take some time; allow time for the update process to complete and do not stop the process once initiated.

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

   # yum update

   Important

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

Procedure

1. Enable the Red Hat Virtualization 4.2 repositories:

   # subscription-manager repos \
       --enable=rhel-7-server-rhv-4.2-manager-rpms \
       --enable=rhel-7-server-rhv-4-manager-tools-rpms \
       --enable=jb-eap-7-for-rhel-7-server-rpms \
       --enable=rhel-7-server-ansible-2.9-rpms

   All other repositories remain the same across Red Hat Virtualization releases.

2. Update the setup packages:

   # yum update ovirt\*setup\*

3. Run engine-setup and follow the prompts to upgrade the Red Hat Virtualization Manager:

   # engine-setup

   Note

   If you changed the default trust keystore password, you might get a keystore certificate error. If so, update the configuration to reflect the correct password. For more information, see RHV 4.2 - Failed to import provider certificate into the external provider keystore

4. Disable the Red Hat Virtualization 4.1 repositories to ensure the system does not use any 4.1 packages:

   # subscription-manager repos \
       --disable=rhel-7-server-rhv-4.1-rpms \
       --disable=rhel-7-server-rhv-4.1-manager-rpms \
       --disable=rhel-7-server-rhv-4-tools-rpms \
       --disable=jb-eap-7.0-for-rhel-7-server-rpms \
       --disable=jb-eap-7.1-for-rhel-7-server-rpms

5. Update the base operating system:

   # yum update

6. Reboot the machine.

7. If Data Warehouse is installed on a separate machine, log in to that machine and restart the ovirt-engine-dwhd service:

   # systemctl restart ovirt-engine-dwhd

Procedure

1. Ensure that the correct repositories are enabled (to view a list of currently enabled repositories, type yum repolist):

   • For Red Hat Virtualization Hosts:

     # subscription-manager repos --enable=rhel-7-server-rhvh-4-rpms

   • For Red Hat Enterprise Linux hosts:

     # subscription-manager repos \
         --enable=rhel-7-server-rpms \
         --enable=rhel-7-server-rhv-4-mgmt-agent-rpms \
         --enable=rhel-7-server-ansible-2.9-rpms

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

3. Click Installation → Check for Upgrade and click OK.

   Click the Events and alerts notification icon ( ) 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 will be migrated according to their migration policy. If migration is disabled for any virtual machines, you will be 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

     If any virtual machines were migrated off the host, they are now migrated back.

     Note

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

Procedure

1. Click Compute → Clusters and select the cluster to change.
2. Click Edit.
3. Change the Compatibility Version to the desired value.
4. Click OK to open the Change Cluster Compatibility Version confirmation window.
5. Click OK to confirm.

Procedure

1. Click Compute → Data Centers and select the data center to change.
2. Click Edit.
3. Change the Compatibility Version to the desired value.
4. Click OK to open the Change Data Center Compatibility Version confirmation window.
5. Click OK to confirm.

1. Log in to the Manager machine as the root user.

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

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

   If it still includes default_md = sha1, back up the existing configuration and change the default to sha256:

   # 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

3. Define the certificate that should be re-signed:

   # names="apache"

4. On the Manager, re-sign the Apache certificate:

   for name in $names; do
       subject="$(
           openssl \
               x509 \
               -in /etc/pki/ovirt-engine/certs/"${name}".cer \
               -noout \
               -subject \
           | sed \
               's;subject= \(.*\);\1;' \
       )"
      /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
           --name="${name}" \
           --password=mypass \
           --subject="${subject}" \
           --keep-key
   done

5. Restart the httpd service:

   # systemctl restart httpd

6. Connect to the Administration Portal to confirm that the warning no longer appears.
7. 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).

1. Log in to the Manager machine as the root user.

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

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

   If it still includes default_md = sha1, back up the existing configuration and change the default to sha256:

   # 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

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

4. Replace the existing certificate with the new certificate:

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

5. Define the certificates that should be re-signed:

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

   If you replaced the Red Hat Virtualization Manager SSL Certificate after the upgrade, run the following instead:

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

   For more details see Replacing the Red Hat Virtualization Manager SSL Certificate in the Administration Guide.

6. On the Manager, re-sign the certificates:

   for name in $names; do
      subject="$(
           openssl \
               x509 \
               -in /etc/pki/ovirt-engine/certs/"${name}".cer \
               -noout \
               -subject \
           | sed \
               's;subject= \(.*\);\1;' \
           )"
        /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
               --name="${name}" \
               --password=mypass \
               --subject="${subject}" \
               --keep-key
   done

7. Restart the following services:

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

8. Connect to the Administration Portal to confirm that the warning no longer appears.
9. 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).

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

    1. In the Administration Portal, click Compute → Hosts.
    2. Select the host and click Management → Maintenance.
    3. Once the host is in maintenance mode, click Installation → Enroll Certificate.
    4. Click Management → Activate.

Procedure

1. Click Administration → Providers and select the OVN provider.
2. Click Edit.
3. Click the Networking Plugin text field and select oVirt Network Provider for OVN from the drop-down list.
4. Click OK.