oVirt 4.2.4 Release Notes

The oVirt Project is pleased to announce the availability of the 4.2.4 Release as of June 26, 2018.

oVirt is a free open-source distributed virtualization solution, designed to manage your entire enterprise infrastructure. oVirt uses the trusted KVM hypervisor and is built upon several other community projects, including libvirt, Gluster, PatternFly, and Ansible.

This release is available now for Red Hat Enterprise Linux 7.5, CentOS Linux 7.5 (or similar).

If you’d like to try oVirt as quickly as possible, follow the instructions on the Download page.

For complete installation, administration, and usage instructions, see the oVirt Documentation.

For a general overview of oVirt, read the About oVirt page.

To learn about features introduced before 4.2.4, see the release notes for previous versions.

No Fedora support

Regretfully, Fedora is not supported anymore, and RPMs for it are not provided. At this point, we only try to fix problems specific to Fedora if they affect developers. For some of the work to be done to restore support for Fedora, see also tracker bug 1460625.

EPEL

Don’t enable all of EPEL on oVirt machines.

The ovirt-release package enables the EPEL repositories and includes several specific packages that are required from there. It also enables and uses the CentOS SIG repos, for other packages.

If you want to use other packages from EPEL, you should make sure to use includepkgs and add only those you need avoiding to override packages from other repos.

What’s New in 4.2.4?

Release Note

oVirt Engine

BZ 1582527 Enable only strong ciphers from engine to VDSM communication for hosts in cluster level >= 4.2

This change enables only string ciphers for communication between engine and hosts for clusters with cluster level >= 4.2.



Following steps need to performed to apply the change:



1. Newly added hosts

- The change is applied automatically when host is added to engine to clusters with cluster level >= 4.2

- When adding new host to cluster with cluster level 3.6, 4.0 or 4.1 the change is not applied and hosts support all ciphers enabled by underlying libraries



2. Existing hosts

- to apply the change to existing hosts in cluster level 4.2 please follow steps described in [How to apply change] section



3. Moving hosts between clusters

- when host is moved to 4.2 cluster the change is not applied automatically. To apply please follow steps described in [How to apply change] section





How to apply change

To enable only strong ciphers for a host in cluster with cluster levels >= 4.2 following steps need to be applied:



1. Move host to Maintenance using option Maintenance in Management menu inside Hosts view

2. Reinstall the host using option Reinstall in Installation menu inside Hosts view

3. Activate the host after successful reinstallation using Activate option in Management menu inside Hosts view

This change enables only string ciphers for communication between engine and hosts for clusters with cluster level >= 4.2. Following steps need to performed to apply the change: 1. Newly added hosts - The change is applied automatically when host is added to engine to clusters with cluster level >= 4.2 - When adding new host to cluster with cluster level 3.6, 4.0 or 4.1 the change is not applied and hosts support all ciphers enabled by underlying libraries 2. Existing hosts - to apply the change to existing hosts in cluster level 4.2 please follow steps described in [How to apply change] section 3. Moving hosts between clusters - when host is moved to 4.2 cluster the change is not applied automatically. To apply please follow steps described in [How to apply change] section How to apply change To enable only strong ciphers for a host in cluster with cluster levels >= 4.2 following steps need to be applied: 1. Move host to Maintenance using option Maintenance in Management menu inside Hosts view 2. Reinstall the host using option Reinstall in Installation menu inside Hosts view 3. Activate the host after successful reinstallation using Activate option in Management menu inside Hosts view BZ 1577593 Disable TLS versions < 1.2 for hosts with cluster level >= 4.1

This change disables TLSv1 and TLSv11 for communication between engine and hosts for clusters with cluster level >= 4.1.



Following steps need to be performed to apply the change:



1. Newly added hosts

- The change is applied automatically when host is added to engine to clusters with cluster level >= 4.1

- When adding new host to cluster with cluster level 3.6 or 4.0 the change is not applied and the host supports TLSv1, TLSv11 and TLSv12 protocols



2. Existing hosts

- to apply the change to existing host in cluster level 4.1 or 4.2 please follow steps described in [How to apply change] section



3. Moving hosts between clusters

- when host is moved to 4.1 or 4.2 cluster the change is not applied automatically. To apply please follow steps described in [How to apply change] section





How to apply change

To disable older TLS versions for a host in cluster with cluster levels >= 4.1 following steps need to be applied:



1. Move host to Maintenance using option Maintenance in Management menu inside Hosts view

2. Reinstall the host using option Reinstall in Installation menu inside Hosts view

3. Activate the host after successful reinstallation using Activate option in Management menu inside Hosts view

Enhancements

oVirt Engine

BZ 1549030 Update neutron binding after VM migration with info from caps

When a port is created/updated, it’s “binding:host_id” attribute should be updated with the id of the provider driver id (for example OVN chassis id) reported during get_caps.

The port for which the binding has been reported, requires the binding to be set on every consecutive host it moves to. This could be a problem when migrating from a 4.2.2 level host to an earlier one.

Hosts before that do not report the host_id. When no provider driver id is reported, the “binding:host_id” is not set, and the value from the previous host will be kept. To fix this, the older hosts need to be updated with a newer version of the provider driver.

When a port is created/updated, it’s “binding:host_id” attribute should be updated with the id of the provider driver id (for example OVN chassis id) reported during get_caps. The port for which the binding has been reported, requires the binding to be set on every consecutive host it moves to. This could be a problem when migrating from a 4.2.2 level host to an earlier one. Hosts before that do not report the host_id. When no provider driver id is reported, the “binding:host_id” is not set, and the value from the previous host will be kept. To fix this, the older hosts need to be updated with a newer version of the provider driver. BZ 1539765 Auto-Sync - network rename on provider does not trigger rename in engine

Feature: External network rename on provider is reflected in engine



Reason: The name of an external network in engine should be consistent with the name of the same network on the provider.



Result: Renaming an external network on the provider is reflected in engine.

Feature: External network rename on provider is reflected in engine Reason: The name of an external network in engine should be consistent with the name of the same network on the provider. Result: Renaming an external network on the provider is reflected in engine. BZ 1098612 [donstream clone 4.2.4] [RFE] filter for “Allocation Policy” in Disks search



BZ 1242822 [RFE] filter for “Allocation Policy” in Disks search



BZ 1251468 [RFE] Additional warning when removing required networks



BZ 1593653 [downstream clone - 4.2.4] [RFE] virtio nics are reported as ‘1gbit’ nics, and should be ‘10gbit’



BZ 1587884 [downstream clone - 4.2.4] [RFE] Include storage domain UUID in Storage Domain ‘General’ tab



BZ 1579302 support more granularity in cluster cpu types

Feature:

Support distinguishing cpus also by features they support, not just by model.



Reason:

If a new CPU feature is important, it is important to be able to distinguish if the CPU with some model also supports this feature and than require this feature also for VMs.



Result:

Now, it is possible to distinguish CPUs also by features and require them for the VMs. CPU types take additional flags in addition to their libvirt name. Like e.g. SandyBridge, you can specify custom CPU as “SandyBridge,+xyz” or “SandyBridge,-xyz” to add or remove arbitrary individual CPU flags in addition to what the named model contains.

Feature: Support distinguishing cpus also by features they support, not just by model. Reason: If a new CPU feature is important, it is important to be able to distinguish if the CPU with some model also supports this feature and than require this feature also for VMs. Result: Now, it is possible to distinguish CPUs also by features and require them for the VMs. CPU types take additional flags in addition to their libvirt name. Like e.g. SandyBridge, you can specify custom CPU as “SandyBridge,+xyz” or “SandyBridge,-xyz” to add or remove arbitrary individual CPU flags in addition to what the named model contains. BZ 1577901 [RFE] add content type column to disk table



oVirt Engine Appliance

BZ 1582507 [downstream clone - 4.2.4] [RFE] Add ovirt-engine-extension-aaa-ldap-setup and ovirt-engine-extension-aaa-ldap to RHV-M Image



oVirt Host Dependencies

BZ 1579210 [downstream clone - 4.2.4] add cockpit-machines-ovirt to RHVH hosts

The cockpit-machines-ovirt plugin (https://cockpit-project.org/guide/latest/feature-ovirtvirtualmachines) has been added to Red Hat Enterprise Linux hosts and Red Hat Virtualization Hosts.

Rebase: Bug Fixeses and Enhancementss

oVirt Engine

BZ 1585157 [downstream clone - 4.2.4] [UI] - VM’s network interface name and icon too large and wrap



Bug Fixes

oVirt Engine

BZ 1583619 [downstream clone - 4.2.4] [SCALE] Listing users in Users tab overloads the postgresql DB (CPU)



BZ 1579719 Geo-Replication failing to kick off geo-rep session daily, when the same volume is used for two different sessions and one gets destroyed.



BZ 1578257 Unable to schedule a Snapshot of a Gluster volume



BZ 1574191 SyncNetworkProviderCommand fails on NPE if Provider is DNP of a Cluster with no DC



BZ 1574451 UI exception seen in ovirt-engine



VDSM

BZ 1584523 [downstream clone - 4.2.4] [HE] Failed to deploy RHV-H on Hosted engine



BZ 1576442 KeyError: ‘sizeTotal’ in gluster volume status monitoring



BZ 1576675 RHV import fails if VM has an unreachable floppy defined



oVirt Engine Metrics

BZ 1572508 fluentd unable to connect keeps retrying every 3 minutes



ovirt-engine-dwh

BZ 1576937 Value too long for type character varying(50) for host_interface_configuration and vm_interface_configuration



oVirt Hosted Engine HA

BZ 1583712 hosted-engine metadata are not correctly read and write on hosts set into maintenance mode from the engine



BZ 1557793 ovirt-hosted-engine-cleanup takes too much time



oVirt Hosted Engine Setup

BZ 1576310 [OVN] - [HE] - ovn tunnel is not created if central hostname resolved as 127.0.0.1 in hosts file



BZ 1557793 ovirt-hosted-engine-cleanup takes too much time



BZ 1557775 [RFE] During deployment, verification is missing for wrong NFS path.



imgbased

BZ 1568414 missing lvm filter causing “nodectl check” to fail to verify thinprovisioned local lv metadata



Other

oVirt Engine

VDSM

BZ 1583045 Failed to add a second host after a successful deployment due to a name clash on vdsm python module



BZ 1570349 After upgrade from 4.1 to 4.2.3 vm disk is inactive and vm nic is un-plugged



BZ 1591667 [downstream clone - 4.2.4] Live storage migration completes but leaves volume un-opened.



BZ 1534197 After updating to current RHV-H, vdsmd consistently fails to start on startup.



BZ 1585030 [downstream clone - 4.2.4] RAW-Preallocated disk is converted to RAW-sparse while cloning a VM in file based storage domain



BZ 1568696 Failed to convert app: [[Ljava.lang.Object;] warning appear in engine.log



BZ 1567603 [CodeChange] Cleanup create snapshot code after requiring qemu > 2.10



BZ 1579909 Cannot start VM with QoS IOPS after host&engine upgrade from 4.1 to 4.2

Vdsm uses the domain metadata section to store extra data which is required to configure a VM but not properly represented on the standard libvirt domain.

This always happens when a VM starts.

Vdsm tried to store the drive IO tune settings in the metadata, which was redundant because the IO tune has already a proper representation.

Furthermore the implementation of the store operation of the IO tune settings had an implementation bug, which made it not possible to succesfully start the VM.

This bug appears only if IO tune settings are enabled.

Vdsm uses the domain metadata section to store extra data which is required to configure a VM but not properly represented on the standard libvirt domain. This always happens when a VM starts. Vdsm tried to store the drive IO tune settings in the metadata, which was redundant because the IO tune has already a proper representation. Furthermore the implementation of the store operation of the IO tune settings had an implementation bug, which made it not possible to succesfully start the VM. This bug appears only if IO tune settings are enabled. BZ 1580478 Vdsm should support hotunplug by Alias



BZ 1565002 Check vdsmd status before starting rpm upgrade



oVirt Engine Metrics

BZ 1585963 Error in collectd 05-global-configuration.conf file - missing end of line



BZ 1573784 Deprecation warning in fluentd forward plugin



ovirt-engine-dwh

BZ 1586011 ovirt-engine-provisiondb should not try to connect to databases



BZ 1573145 Update hosts and vms receive_rate_percent and transmit_rate_percent network statistics precision

Cause:

The precision of the rx_rate, tx_rate of virtual and host network interfaces has been increased on the engine db.



Consequence:

This requires updating the dwh precision for better reporting.



Fix:

Update hosts and vms receive_rate_percent and transmit_rate_percent network statistics precision



Result:

Hosts and vms receive_rate_percent and transmit_rate_percent network statistics precision was increased on DWH.

oVirt Hosted Engine HA

BZ 1585028 [downstream clone - 4.2.4] RHV-H 4.2.3: hosted-engine agent fails to start after upgrade due to Permission denied: ‘/var/log/ovirt-hosted-engine-ha/broker.log’ ‘/var/log/ovirt-hosted-engine-ha/agent.log’



oVirt Hosted Engine Setup

BZ 1578418 Checks on bond mode are not effective



BZ 1594024 [HE] Failed to deploy hosted engine over NFS on updated rhel7.5 with ansible 2.6



BZ 1578404 Fetch engine logs from the engine VM



BZ 1573074 The deployment fails on create_storage_domain stage when using generated answers



BZ 1576451 ovirt-hosted-engine-cleanup must undefine the HostedEngine VM



cockpit-ovirt

BZ 1582579 Using a new device for creating non vdo volume is being blocked



BZ 1583637 HE Wizard - General error message displayed with no field-specific errors



oVirt Engine SDK 4 Java

BZ 1434834 Implement automatic SSO token renew



BZ 1571648 Detailed message in Error SDK



oVirt Log Collector

BZ 1573143 Collect ovirt-provider-ovn logs.



OTOPI

BZ 1574433 “Invalid data received during bootstrap” errors do not log the invalid data



oVirt Provider OVN

BZ 1580254 removing routers external_gateway by port leaks static_routes



BZ 1559056 Provider does not check if generated port MAC address is already assigned



imgbased

BZ 1585028 [downstream clone - 4.2.4] RHV-H 4.2.3: hosted-engine agent fails to start after upgrade due to Permission denied: ‘/var/log/ovirt-hosted-engine-ha/broker.log’ ‘/var/log/ovirt-hosted-engine-ha/agent.log’



BZ 1589544 [HE] host-deploy fails to start vdsmd on node/rhel-h



BZ 1534197 After updating to current RHV-H, vdsmd consistently fails to start on startup.



oVirt Node

BZ 1534197 After updating to current RHV-H, vdsmd consistently fails to start on startup.



VDSM JSON-RPC Java

BZ 1571768 Connections shouldn’t be closed after the connection to the host was recovered



oVirt Engine

BZ 1422428 [fr-FR] Admin portal->Quota: measurements units are mixed up (GB in English and Go in French all mixed up).



BZ 1542341 [fr, de, es] A button label on administration ->quota -> add page is getting truncated.



BZ 1542880 [fr, es, pt_BR, ja] Text alignment correction needed on compute -> virtual machines -> affinity groups -> new page



BZ 1541309 [ja_JP] Text Positioning needs to be adjusted on Administration -> Quota -> add screen.



BZ 1541348 [ja, zh_CN, ko] Text positioning needs to be adjusted on Administration - Configure -> scheduling policy -> new page



BZ 1576752 Number of “Prestarted VMs” is ignored and all VMs of Pool starts after editing existing Pool.



BZ 1582356 UI hangs with NPE while trying to migrate VM in Powering Up status



oVirt Hosted Engine HA

BZ 1571119 [HE] - Engine complaining that the ‘VM HostedEngine is down with error. Exit message: resource busy: Failed to acquire lock: Lease is held by another host.’



BZ 1582489 Memory leak, at least 7.31 KB per minute



oVirt Hosted Engine Setup