4.6. Red Hat Virtualization 4.3 Batch Update 5 (ovirt-4.3.8)

BZ#1754979

Previously, upgrading RHV Manager from 4.2 to 4.3 ovirt-fast-forward-upgrade sometimes failed with a yum dependency error if engine-setup was not executed following the yum update of the 4.2. That was causing an inconsistent state of the system, preventing it from upgrading to 4.3. The current version fixes this issue.

BZ#1757423

Normally, when the "UserSessionTimeOutInterval" is set to a negative value such as "-1", the user remains logged into the VM Portal indefinitely. However, in RHV version 4.5.3.6, a negative value automatically logged the user out immediately. The current release fixes this issue, such that, with the value set to -1, the user is never automatically logged out, as expected per the config value definition in ovirt-engine engine-config.properties: "A negative value indicates that sessions never expire.": https://github.com/oVirt/ovirt-engine/blob/e0940bd9b768cb52c78f9e0d0c97afd6de7ac8a5/packaging/etc/engine-config/engine-config.properties#L218-L220

BZ#1765912

Previously, VDSM v4.30.26 added support for 4K block size with file-based storage domains to Red Hat Virtualization 4.3. However, there were a few instances where 512B block size remained hard-coded. These instances impacted the support of 4K block size under certain conditions. This release fixes these issues.

BZ#1773580

Previously, when you used the VM Portal to create a Windows virtual machine, it failed with the following error "CREATE_VM failed [Cannot add VM. Invalid time zone for given OS type., Attribute: vmStatic]." The Administration Portal did not have this issue. The current release fixes this issue.

BZ#1779664

Previously, when you deleted a snapshot of a VM with a LUN disk, its image ID parsed incorrectly and used "mapper" as its value, which caused a null pointer exception. The current release fixes this issue by avoiding disks whose image ID parses as 'mapper' so deleting the VM snapshot is successful.

BZ#1780290

When sharding was enabled and a file’s path had been unlinked, but its descriptor was still available, attempting to perform a read or write operation against the file resulted in the host becoming non-operational. File paths are now unlinked later, avoiding this issue.

BZ#1781380

Previously, after using the REST API to create an affinity group, the resulting group did not have the required labels, even though they were defined in the request body. The current release fixes this issue so the affinity group has the labels that were defined in the request body.

BZ#1739106

This release adds a new feature, rhv-image-discrepancies, which reports discrepancies between images in the engine database and storage. The report lists images that are present in one location but missing from the other. Also, for images that are present in both locations, the report lists discrepancies in the values of attributes such as status, parent_id, and type.

BZ#1767333

This release adds a new 'status' column to the affinity group table that shows whether all of an affinity group’s rules are satisfied (status = ok) or not (status = broken). The "Enforcing" option does not affect this status.

BZ#1779160

To avoid overloading the journal log, in this release, oVirt Guest Agent no longer attempts to query the list of containers on machines without Docker.

BZ#1782412

In the current release, Metrics Store adds support for a flat DNS environment without subdomains. This capability helps you satisfy security policies that mandate having a "flat" DNS environment with no submains. To enable this capability, you add a suffix to the master0 virtual machine when you configure networking for Metrics Store virtual machines. For example, if you set 'openshift_ovirt_machine_suffix' to 'prod' and 'public_hosted_zone' is 'example.com', then the metrics store virtual machine will be called 'master-prod0.example.com'.