- Issued:
- 2017-11-07
- Updated:
- 2017-11-07
RHEA-2017:3139 - VDSM bug fix and enhancement update 4.1.7
Synopsis
VDSM bug fix and enhancement update 4.1.7
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, incorrect LVM configuration resulted in incorrect LVM output. The LVM configuration has now been fixed so that the correct LVM output is generated. The names of the generated files are as follows:
lvm_lvs_-v_-o_tags_--config_global_locking_type_0_use_lvmetad_0_devices_preferred_names_.dev.mapper.ignore_suspended_devices_1_write_cache_state_0_disable_after_error_count_3_filter_a.dev.mapper.._r
lvm_pvs_-v_-o_all_--config_global_locking_type_0_use_lvmetad_0_devices_preferred_names_.dev.mapper.ignore_suspended_devices_1_write_cache_state_0_disable_after_error_count_3_filter_a.dev.mapper.._r
lvm_vgs_-v_-o_tags_--config_global_locking_type_0_use_lvmetad_0_devices_preferred_names_.dev.mapper.ignore_suspended_devices_1_write_cache_state_0_disable_after_error_count_3_filter_a.dev.mapper.._r (BZ#1483328)
-
Previously, VDSM expected the optional object identifier OID field in Link Layer Discovery Protocol (LLDP). If this was absent, parsing of LLDP failed. Now, VDSM no longer expects the object identifier OID field in LLDP. LLDP info from the host is presented via the REST API without an object identifier OID. (BZ#1496677)
-
Previously, when copying disks using qcow2 compressed format, the destination disk size was not calculated correctly, because it was incorrectly assumed that the disk was not compressed. Copying an uploaded disk using qcow2 compressed format, or cloning a virtual machine using such disk, would fail. Now, the system estimates the destination disk size based on the qcow2 actual image format, so it is possible to copy compressed disks and clone virtual machines that use them. (BZ#1503219)
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
| Product | Version | Arch |
|---|---|---|
| Red Hat Virtualization | 4 | x86_64 |
| Red Hat Virtualization for IBM Power LE | 4 | ppc64le |
Updated Packages
- vdsm-hook-fcoe-4.19.36-1.el7ev.noarch.rpm
- vdsm-hook-localdisk-4.19.36-1.el7ev.noarch.rpm
- vdsm-hook-macspoof-4.19.36-1.el7ev.noarch.rpm
- vdsm-hook-extra-ipv4-addrs-4.19.36-1.el7ev.x86_64.rpm
- vdsm-hook-openstacknet-4.19.36-1.el7ev.noarch.rpm
- vdsm-hook-vfio-mdev-4.19.36-1.el7ev.noarch.rpm
- vdsm-hook-checkips-4.19.36-1.el7ev.ppc64le.rpm
- vdsm-hook-extra-ipv4-addrs-4.19.36-1.el7ev.ppc64le.rpm
- vdsm-4.19.36-1.el7ev.ppc64le.rpm
- vdsm-jsonrpc-4.19.36-1.el7ev.noarch.rpm
- vdsm-hook-nestedvt-4.19.36-1.el7ev.noarch.rpm
- vdsm-python-4.19.36-1.el7ev.noarch.rpm
- vdsm-api-4.19.36-1.el7ev.noarch.rpm
- vdsm-gluster-4.19.36-1.el7ev.noarch.rpm
- vdsm-4.19.36-1.el7ev.x86_64.rpm
- vdsm-yajsonrpc-4.19.36-1.el7ev.noarch.rpm
- vdsm-client-4.19.36-1.el7ev.noarch.rpm
- vdsm-cli-4.19.36-1.el7ev.noarch.rpm
- vdsm-hook-vhostmd-4.19.36-1.el7ev.noarch.rpm
- vdsm-hook-vmfex-dev-4.19.36-1.el7ev.noarch.rpm
- vdsm-4.19.36-1.el7ev.src.rpm
- vdsm-hook-ethtool-options-4.19.36-1.el7ev.noarch.rpm
- vdsm-hook-checkips-4.19.36-1.el7ev.x86_64.rpm
- vdsm-xmlrpc-4.19.36-1.el7ev.noarch.rpm
Fixes
- This content is not included.BZ - 1463218
- This content is not included.BZ - 1483328
- This content is not included.BZ - 1496677
- This content is not included.BZ - 1497940
- This content is not included.BZ - 1502213
- This content is not included.BZ - 1503219
- This content is not included.BZ - 1506161
CVEs
(none)
References
(none)
Additional information
- The Red Hat security contact is This content is not included.secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.
- Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.