RHEA-2017:0998 - Product Enhancement Advisory

Topic

Updated vdsm packages that fix several bugs and add various enhancements are now available.

Description

VDSM is a management module that serves as a Red Hat Virtualization Manager agent on Red Hat Virtualization Host or Red Hat Enterprise Linux hosts.

Changes to the vdsm component:

• Previously, Red Hat Virtualization could not import an OVA from VMWare when the destination storage domain used block storage. Allocating a smaller size for the VM disk by reading the 'size' attribute of the OVF XML caused the import to fail with no good reason. Now, the import operation uses the 'physical size' attribute for disk allocation, so an OVA can be imported to a block storage domain. (BZ#1382404)
• This update fixes an error in the monitoring code that caused VDSM to incorrectly report that a QEMU process had recovered and was responsive after being unavailable for a short amount of time, while it was actually unresponsive. (BZ#1361028)
• Previously, if a VM shutdown was too slow, the state of the VM could be misreported as unresponsive, even though the VM was operating correctly, albeit too slowly. This was caused by a too-aggressive check on startup and shutdown. This patch takes into account slowdowns in startup and shutdown, avoiding false positive reports. (BZ#1382578)
• Previously, NUMA sampling could cause an unnecessarily high load on a complex host. This update reduces the sample interval to 10 minutes, as that is enough for rarely-changing NUMA topology. (BZ#1396910)
• Previously, VDSM 4.0 didn't support a 3.5 Manager, but reported it as supported; you could add a 4.0 host to a 3.5 Manager, but would experience failures. This release removes 3.5 from the supported Manager versions, so you can not add a 4.0 host to a 3.5 Manager. (BZ#1403835)
• Previously, the Manager didn't send migration limits to VDSM during VM migration operations. The destination VDSM understood this lack of migration limits as migration from an old source that didn't support the retry logic, failing the migration altogether instead of having the source attempt a proper retry. This could ultimately result in the host entering an error state; especially problematic, for example, when attempting to put a host to maintenance.

Now, the Manager sends migrations limits as part of the VM migration operation, so the migration retry logic between the source and destination VDSM is properly triggered when necessary. (BZ#1409246)

Solution

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

For details on how to apply this update, refer to:

https://access.redhat.com/articles/2974891

Affected Products

• Red Hat Virtualization 4 for RHEL 7 x86_64
• Red Hat Virtualization for IBM Power LE 4 for RHEL 7 ppc64le

Fixes

• BZ - 1081962 - [SCALE] block storage domain monitoring thread slows down when storage operations are running
• BZ - 1223538 - VDSM reports "lvm vgs failed" warning when DC contains ISO domain
• BZ - 1236161 - VDSM response to path preparation during live VM migration was very slow
• BZ - 1242532 - vdsm fails to start if one network fails to be restored
• BZ - 1326940 - After ovirt-engine is restarted, hypervisors stop listening on 54321 until vdsm is restarted.
• BZ - 1344890 - Failed to add rhel7.3 to rhevm4.0 as failed to start vdsmd service
• BZ - 1357798 - VMs are not reported as non-responding even though qemu process does not responds.
• BZ - 1361028 - VMs flip to non-responsive state for ever.
• BZ - 1372093 - vdsm sos plugin should collect 'nodectl info' output
• BZ - 1374545 - Guest LVs created in ovirt raw volumes are auto activated on the hypervisor in RHEL 7
• BZ - 1377157 - LVM cache not updating and reporting unknown device
• BZ - 1381009 - Cisco UCS fencing using "Power fencing policy" in RHEVM is not shutting down the fence device.
• BZ - 1382404 - Importing VMs from VMware ova file fails with block storage domain and thin provisioned disk
• BZ - 1382578 - Periodic functions may continue running after VM is down.
• BZ - 1382583 - Periodic functions/monitor start before VM is run.
• BZ - 1393458 - Error in slot allocation when adding a new disk volume
• BZ - 1396910 - Numa sampling causes very high load on the hypervisor.
• BZ - 1397490 - bond mode 4 default xmit_hash_policy wrong
• BZ - 1398572 - hostdev listing takes large amount of time
• BZ - 1398822 - HE VM shutdown abruptly when master storage domain is put into maintenance mode (VDSM side)
• BZ - 1400528 - [Bug RHV 4.0.4] Intermittent direct lun vm failed to start with error "VolumeError: Bad volume specification".
• BZ - 1403835 - Remove 3.5 from the supportedEngines reported by VDSM
• BZ - 1403846 - keep 3.6 in the supportedEngines reported by VDSM
• BZ - 1406651 - setupNetworks fails if there is an empty line in the ifcfg files
• BZ - 1406851 - Live disk migration failed with: block copy still active: disk 'vda' not ready for pivot yet
• BZ - 1409246 - VM migration failing with "Returning backwards compatible migration error code"
• BZ - 1416278 - schema inconsistencies flooding logs
• BZ - 1426440 - During Live Merge, clear information about top/base/active volumes is not provided by INFO level logging

CVEs

(none)

References

(none)