Issued:
2017-03-16
Updated:
2017-03-16

RHBA-2017:0544 - vdsm 4.0.7 bug fix and enhancement update

Synopsis

vdsm 4.0.7 bug fix and enhancement update

Type/Severity

Bug Fix Advisory None

Topic

Updated vdsm packages 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, the lvmetad daemon dynamically activated logical volumes on multipath devices including logical volumes created inside the virtual machine on top of Red Hat Virtualization Manager’s (RHV) logical volumes. This caused many issues, including the following:
  • Increasing the number of devices on the Red Hat Virtualization Host, slowing down any operation that needed to enumerate or scan devices.
  • Failure to deactivate RHV logical volumes because the guest logical volumes on top of them were active. This could lead to data corruption.
  • Errors when running lvm commands on the host, because guest logical volumes may use physical volumes not available on the Red Hat Virtualization Host.

In this release, VDSM disables the lvmetad service and logical volumes are no longer activated dynamically. VDSM activates and deactivates the logical volumes as needed. (BZ#1398918)

  • Previously, the sanlock library did not handle interrupted system calls correctly. As a result, if a vdsm child process was terminated while the vdsm was blocked on a sanlock call, the call was interrupted and failed. Now, the sanlock library correctly handles interrupted system calls and sanlock calls do not fail if a child process is terminated during a sanlock call. (BZ#1416336)

  • Previously, it was possible to add a 4.0 VDSM to a 3.5 Manager. However, this led to failures. Now, it is no longer possible to add a 4.0 VDSM to a 3.5 Manager. (BZ#1405758)

  • Previously, the Manager did not send migration limitations to the VDSM during virtual machine migration operations, to define the maximum number of concurrent incoming and outgoing operations. As a result, if one of these limits was reached by the VDSM, it did not attempt to retry the operation that failed. Now, the Manager sends the migration limitations to the VDSM as part of each migration operation, and consequently, if one of the limits is reached, the VDSM will retry when the required capacity becomes available. (BZ#1413939)

  • Previously, when a LUN was discovered by a host, LVM activated a logical volume on the LUN before the LUN could be mapped by multipath. As result, the multipath device was not available on the host, and virtual machines could not use the missing device. Now, LVM no longer activates logical volumes dynamically, and multipath can successfully map the LUN. (BZ#1424819)

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/11258

Affected Products

ProductVersionArch
Red Hat Virtualization4x86_64
Red Hat Virtualization for IBM Power LE4ppc64le

Updated Packages

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

Fixes

CVEs

(none)

References

(none)

Additional information