RHBA-2017:0544 - Bug Fix Advisory

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

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

Fixes

• BZ - 1398918 - [z-stream clone - 4.0.7] All LVs are auto activated on the hypervisor in RHEL 7
• BZ - 1405758 - [z-stream clone - 4.0.7] Remove 3.5 from the supportedEngines reported by VDSM
• BZ - 1405802 - [z-stream clone - 4.0.7] hostdev listing takes large amount of time
• BZ - 1409478 - [z-stream clone - 4.0.7] Importing VMs from VMware ova file fails with block storage domain and thin provisioned disk
• BZ - 1413939 - [z-stream clone - 4.0.7] VM migration failing with "Returning backwards compatible migration error code"
• BZ - 1416336 - consume fix for "Bug 1356667: libsanlock does not handle EINTR, causing failures in client" to be released 2016-Sep-13
• BZ - 1418280 - [4.0.z] Improve logging during live merge
• BZ - 1424819 - [downstream clone - 4.0.7] [Bug RHV 4.0.4] Intermittent direct lun vm failed to start with error "VolumeError: Bad volume specification".

CVEs

(none)

References

(none)