Bug Fix Advisory vdsm 4.0.7 bug fix and enhancement update

Advisory: RHBA-2017:0544-1
Type: Bug Fix Advisory
Severity: N/A
Issued on: 2017-03-16
Last updated on: 2017-03-16
Affected Products: Red Hat Virtualization ( v.4 for RHEL 7)

Details

Updated vdsm packages are now available.

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

Updated packages

Red Hat Virtualization ( v.4 for RHEL 7)

SRPMS:
vdsm-4.18.24-3.el7ev.src.rpm     MD5: bac8477988ca74ceb712a1e885497149
SHA-256: 536cb3b6c2ae359f36ab325690fee6a5bcce70c3ee44503a27cacb9b9e66accd
 
x86_64:
vdsm-4.18.24-3.el7ev.x86_64.rpm     MD5: 175607842bca0d3d7dd13f73a7f09b0e
SHA-256: fe58bcee5936be2f6f3d06d9897ca76b280d36a4bbdf6b9bdfd71c07bf3aafea
vdsm-api-4.18.24-3.el7ev.noarch.rpm     MD5: 6af39597a27802bae6b50ca4efb9aa83
SHA-256: 5551d52f2b807d474f68c14444ac8419e4a078276847f64beda93e8a07f7691a
vdsm-cli-4.18.24-3.el7ev.noarch.rpm     MD5: 0d438e4d82192a0998dec0842670076c
SHA-256: cb989c42178510a51bd7aa4579a318d99877a35a9c3f3a3e0d6518df0c186faa
vdsm-gluster-4.18.24-3.el7ev.noarch.rpm     MD5: 73f10a504c4bd1cf7789f7b1215d393d
SHA-256: 9f05989b23e811df6a69715ca035d4c1c19a8589f216bec98920e59bed957546
vdsm-hook-ethtool-options-4.18.24-3.el7ev.noarch.rpm     MD5: 5492f9d0b442a119ddecbde85d1f8ec7
SHA-256: a10203a4d184632b9450a3d7a67a21516646b2cb10e0208a8819fa8a01e25010
vdsm-hook-fcoe-4.18.24-3.el7ev.noarch.rpm     MD5: ef679f1a8f13818466017dbfabf56055
SHA-256: 5d304087ac695cdc4fb562475f2707b6afdf01140410a3980ccd975e1a3e8030
vdsm-hook-macspoof-4.18.24-3.el7ev.noarch.rpm     MD5: a7ca5e578b3489e61323a5d5e1af5ceb
SHA-256: a1d5655f3c05e309ddaa10a857c7e26f86d1849bcd35eceb06276d81bbb82f3d
vdsm-hook-openstacknet-4.18.24-3.el7ev.noarch.rpm     MD5: 4cf951b8c964b2fabd116efeeba240e5
SHA-256: 5d202c3c9bd857b33df70172e70081bda7af415d74996b961153ce4831988fbc
vdsm-hook-vhostmd-4.18.24-3.el7ev.noarch.rpm     MD5: 71ff078bbd44a20130182689e88ac545
SHA-256: 03dca8a73dcafebe01dd601509f0d7ce1fa19172922e5f055197bf463aaa9578
vdsm-hook-vmfex-dev-4.18.24-3.el7ev.noarch.rpm     MD5: 53c933be806f26599e4526b914537213
SHA-256: 3b547b056f15293a9a213aba32f197fd28f906915dee767c2217512121de4b72
vdsm-infra-4.18.24-3.el7ev.noarch.rpm     MD5: 0fae8022309be74be8f847f4bffb4a28
SHA-256: 2a70a12747fc0959b82bd114780ee892454ee115ef12071dc15c8104e141febd
vdsm-jsonrpc-4.18.24-3.el7ev.noarch.rpm     MD5: 5109b9dcb7218da411db87dea87e015e
SHA-256: 35e1e68a0a588f3b85a35041405afc0e757eb748d5ee1e08b9941861f6804bc9
vdsm-python-4.18.24-3.el7ev.noarch.rpm     MD5: 6011bcc5893c873ba8e6b0be4983c239
SHA-256: 4913a49e972b8149dce08f26800435c1288f08b99d20f93ea8f61de1e6a3b218
vdsm-xmlrpc-4.18.24-3.el7ev.noarch.rpm     MD5: 38cdf2db71484253b5af952e6c087a28
SHA-256: f4f0c8ced70b9b574bd642bfc18413172e7219f329f97388329f74edd6399bd8
vdsm-yajsonrpc-4.18.24-3.el7ev.noarch.rpm     MD5: 2e86c23ef0d07ca66cdb1182c6291e20
SHA-256: cb0d90d67bef9966156c135f1f83f2be26d0c97f9ee83acfd1d7631e8d4a794d
 
(The unlinked packages above are only available from the Red Hat Network)

Bugs fixed (see bugzilla for more information)

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


Keywords

vdsm-4.18


These packages are GPG signed by Red Hat for security. Our key and details on how to verify the signature are available from:
https://www.redhat.com/security/team/key/#package

The Red Hat security contact is secalert@redhat.com. More contact details at http://www.redhat.com/security/team/contact/