Issued:
2017-04-18
Updated:
2017-07-17

RHEA-2017:0998 - VDSM bug fix and enhancement update 4.1 GA

Synopsis

VDSM bug fix and enhancement update 4.1 GA

Type/Severity

Product Enhancement Advisory None

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

ProductVersionArch
Red Hat Virtualization4x86_64
Red Hat Virtualization for IBM Power LE4ppc64le

Updated Packages

  • vdsm-client-4.19.10.1-1.el7ev.noarch.rpm
  • vdsm-hook-ethtool-options-4.19.10.1-1.el7ev.noarch.rpm
  • vdsm-hook-vmfex-dev-4.19.10.1-1.el7ev.noarch.rpm
  • vdsm-hook-openstacknet-4.19.10.1-1.el7ev.noarch.rpm
  • vdsm-xmlrpc-4.19.10.1-1.el7ev.noarch.rpm
  • vdsm-4.19.10.1-1.el7ev.src.rpm
  • vdsm-hook-fcoe-4.19.10.1-1.el7ev.noarch.rpm
  • vdsm-4.19.10.1-1.el7ev.ppc64le.rpm
  • vdsm-hook-vhostmd-4.19.10.1-1.el7ev.noarch.rpm
  • vdsm-gluster-4.19.10.1-1.el7ev.noarch.rpm
  • vdsm-python-4.19.10.1-1.el7ev.noarch.rpm
  • vdsm-api-4.19.10.1-1.el7ev.noarch.rpm
  • vdsm-cli-4.19.10.1-1.el7ev.noarch.rpm
  • vdsm-yajsonrpc-4.19.10.1-1.el7ev.noarch.rpm
  • vdsm-4.19.10.1-1.el7ev.x86_64.rpm
  • vdsm-hook-macspoof-4.19.10.1-1.el7ev.noarch.rpm
  • vdsm-jsonrpc-4.19.10.1-1.el7ev.noarch.rpm

Fixes

CVEs

(none)

References

(none)

Additional information