4.5. Red Hat Virtualization 4.3 Batch Update 4 (ovirt-4.3.7)

4.5.1. Bug Fix

The items listed in this section are bugs that were addressed in this release:


The Windows Guest Tools ISO was automatically attached to a Windows virtual machine even when it was an older version. In this release the ISO version is checked in the data domains and the ISO domains, and the ISO is automatically attached only if it is a newer version than the existing one.


When importing a KVM in RHV, "Hardware Clock Time Offset" was not set. In this release a default engine setting is set for the "Hardware Clock Time Offset" field. As a result, the engine will recognize the guest agent on a virtual machine imported from KVM.


On a self-hosted Red Hat Virtualization Manager, ovirt-ha-broker restarts if it encounters an issue reading or writing to storage. Previously, in some cases, this caused VDSM to get stuck and report the status of the host as "Not Responding" and "Connecting" until the user restarted the Manager. The workaround for this issue was to restart the Manager. The current release mitigates this issue by adding a 5-seconds delay before VDSM sends a report to the Manager that a host is down.


Read permissions were not restricted in 10-setup-ovirt-provider-ovn.conf In this release, only the necessary read permissions are defined.


Previously, with Red Hat Virtualization 4.3 on RHEL 7, if the system had Python 3 installed, otopi used Python 3. This caused relevant tools such as engine-setup and ovirt-host-deploy to fail. The current release fixes this issue: Now, even with Python 3 installed, otopi uses Python 2, enabling otopi-based tools such as engine-setup and ovirt-host-deploy to succeed. In the next minor version, 1.9, otopi should support Python 3 on RHEL 8 and Fedora.


The Administration Portal showed very high memory usage for a host with no VMs running. As a result, VMs could not be migrated to that host. In this release, the free host memory is evaluated correctly.


Previously, when a system had many Fibre Channel (FC) LUNs with many paths per LUN and a high I/O load, scanning of FC devices became slow. This caused timeouts in monitoring virtual machine disk size and made virtual machines non-responsive. The current release mitigates this issue by optimizing FC scans for speed, and VM are much less likely to become non-responsive.


Previously, using LUKS alone was a problem because the Red Hat Virtualization Manager could reboot a node using Power Management commands. However, the node would not reboot because it was waiting for the user to enter a decrypt/open/unlock passphrase. This release fixes the issue by adding clevis RPMs to the Red Hat Virtualization Host (RHVH) image. As a result, a Manager can automatically unlock/decrypt/open an RHVH using TPM or NBDE.


After updating the IPv6 gateway, the host IPv6 default route was not defined. In this release, the IPv6 Default Route is configured correctly following an IPv6 gateway update


A missing alias name prevented the Virtual Desktop Server Manager from identifying the VNIC which required a hot unplug. As a result, the hot unplug failed. In this release, if an alias name is not defined in the RHV Manager, it will be generated on the fly, and the hot unplug will succeed.


Previously, stopping, killing, or restarting the VDSM service on the Storage Pool Manager (SPM VDSM) while performing a live storage migration risked corrupting the virtual disk data. The current release removes ExecStopPost from the VDSM service to help prevent data corruption on virtual disks during live storage migration.


Previously, NICs on a Red Hat Virtualization Host you had configured to remain off were turned back on after rebooting. This happened because a bug expanded %{_libdir} to /usr/lib64 instead of /usr/lib and failed to disable clevis. The current release fixes this bug so that these NICs remain off.


Previously, NICs on a Red Hat Virtualization Host you had configured to use "Shared" or "Link-local" mode did not apply the configuration after reboot. The current release fixes this issue and uses the selected mode after rebooting.

4.5.2. Enhancements

This release of Red Hat Virtualization features the following enhancements:


In this release, support has been added for OpenSCAP security profiles that can be enabled during self-hosted engine deployment.


The following improvements have been made to host certificates used for encrypted communication between the RHV Manager and the Virtual Desktop Server Manager: 1. All newly added host will have certificates with correct SAN field 2. A periodic check for certificate validity is performed and if the SAN field is not populated an error is reported in the audit log, notifying administrators that the host certificate needs to be re-enrolled. 3. The SAN field in the certificate is also checked during host upgrade, so that the host certificate can be re-enrolled during host upgrade.

4.5.3. Rebase: Bug Fixes and Enhancements

The items listed in this section are bugs or enhancements that were originally resolved or introduced in the community version and included in this release.


This release upgrades ovirt-provider-ovn to version 1.2.27.


This release upgrades otopi to version 1.8.4.


This release upgrades ovirt-host-deploy to version 1.8.4.


This release upgrades ovirt-hosted-engine-ha to version 2.3.6.

4.5.4. Deprecated Functionality

The items in this section are either no longer supported or will no longer be supported in a future release.


The APT service, used by the Red Hat Virtualization Guest Tools for Windows virtual machines, is deprecated in Red Hat Virtualization 4.3.7, and will be removed in Red Hat Virtualization 4.4 because: - RHV 4.2 removed the automatic upgrading of guest tools, because the APT service subsequently caused a forced reboot of the virtual machine without a confirmation prompt, possibly causing data loss. - Red Hat Virtualization 4.4 will use the virtio-win installer, which requires re-factoring to continue supporting the APT service.