第2章 RHBA-2017:0542 Red Hat Virtualization Manager 4.0.7

ovirt-engine

BZ#1400043

This bug fixes several issues with insufficient synchronization when accessing MAC pools.

BZ#1400564

Red Hat OpenStack Platform 10 is now a certified external network provider for Red Hat Virtualization.

BZ#1402822

A bug was discovered in the sysprep templates for 64-bit platforms where some parts were improperly marked as "for 32-bit platform" and thus ignored by Windows. This has now been fixed.

BZ#1416346

This release adds support for specifying the initial size through the API when creating a thin provisioned disk on block storage.

BZ#1420726

With this update, the issue where an incorrect calculation meant that virtual machines with an unsupported number of vCPUs attempted to start and failed has been fixed. The maximum number of allowed vCPUs per virtual machine formula was adjusted to take into account the limitation of APIC ID. For more information see https://software.intel.com/en-us/articles/intel-64-architecture-processor-topology-enumeration

BZ#1421725

With this update, an exception displayed in certain cases when editing virtual machine pools has been fixed.

BZ#1422470

Previously, when restoring a backup of a self-hosted engine on a different environment, for disaster recovery purposes, administrators were sometimes required to remove the previous self-hosted engine's storage domain and virtual machine. This was accomplished from within the engine's database, which is a risk-prone procedure.
In this release, a new CLI option enables administrators to remove the previous self-hosted engine's storage domain and virtual machine directly from the backup of the engine, during the restore procedure.

BZ#1422486

Self-hosted engine always uses an SPM ID of 1 during installation of the first self-hosted engine host, without checking database settings. This release adds options to change the database during the restore process.
For disaster recovery, the --he-remove-hosts option has been added so that all hosts with SPM_ID=1 are updated and a different SPM ID assigned.
For bare metal to self-hosted engine migration, a new engine-migrate-he.py script is provided. This script should be called before migration, and supplied with the Manager REST API login/password/endpoint and path to CA certificate. Hosts in the selected data center with SPM_ID=1 will be put into Maintenance mode, so they can accept the new ID safely. Migration can then continue as usual, using the --he-remove-hosts option.

BZ#1425893

Previously, restoring a self-hosted engine backup failed if the self-hosted engine storage domain contained disks associated to virtual machines other than the self-hosted engine one. This has now been fixed.

BZ#1427158

Previously, attempting to drag icons from elements that were not drag-and-drop enabled caused an exception to be thrown due to a missing empty check on a string pulled from the drag event data. An error would be displayed to the user, requiring a page refresh to clear it. Now, the string pulled from the drag event data is checked for nullness/emptiness, so the exception and error are avoided.

BZ#1413970

Previously, there were frequent KeyError tracebacks in the vdsm.log after CPU hotplug. Now, these errors are no longer produced by VDSM after CPU hotplug.

BZ#1425900

Previously, attaching a live storage domain after restoring the database caused sanlock to kill the self-hosted engine virtual machine. This has now been fixed.

BZ#1430296

Previously, the 'VM evenly distributed' policy was not properly taking the pending virtual machines (scheduled, but not yet started) into account. Each scheduling run saw the same situation and selected the same host for the virtual machine it was scheduling. Now, the policy also counts pending virtual machines, so proper balancing is applied.

BZ#1386610

This release introduces a 'force' flag, which can be used to update a storage server connection regardless of the associated storage domain status (allowing updates even when the storage domain is not in Maintenance mode). 

For example: PUT /ovirt-engine/api/storageconnections/123;force=true

BZ#1401848

Previously, some OVF files that did not contain the VM Name tag caused a runtime error when importing. This update ensures that a default name is provided to the virtual machine by its OVA name.

BZ#1416050

This update fixes an issue where engine-setup would not run over a restored database if the backup was taken from a hosted-engine environment that was not in global maintenance mode.

BZ#1416308

This update adds a connection pool to reuse existing connections for communication between the Manager and the SSO module.
By default, a connection pool is created on the Manager to communicate with the SSO module. The size of this pool is defined by the ENGINE_SSO_SERVICE_CLIENT_POOL_SIZE option (default size is 10 connections). Similarly, a connection pool is created on the SSO side to communicate with the Manager. The size of this pool is defined by the SSO_CALLBACK_CLIENT_POOL_SIZE option (default size is 10 connections). 
If needed, these options can be customized by creating the /etc/ovirt-engine/engine.conf.d/99-custom-connection-pool.conf file with the following (where N and M are the new sizes):

ENGINE_SSO_SERVICE_CLIENT_POOL_SIZE=N
SSO_CALLBACK_CLIENT_POOL_SIZE=M

BZ#1419540

Previously, the Manager tried to negotiate the highest available version of TLS when connecting to VDSM. However, due to certain limitations the Manager tried to negotiate TLSv1.0 as the highest version. Now, the limitations have been removed and the Manager is able to negotiate TLSv1.1 and TLSv1.2 when they are available on VDSM. Removing these limitations also enables providing only newer TLS versions in future VDSM versions.

BZ#1425890

Previously, restoring a self-hosted engine backup failed if the self-hosted engine host had running non-self-hosted engine VMs. This has now been fixed.