Updated vdsm packages that fix several bugs and add various enhancements are nowavailable.

VDSM is a management module that serves as a Red Hat Enterprise VirtualizationManager agent on Red Hat Enterprise Virtualization Hypervisor or Red HatEnterprise Linux hosts.Changes to the vdsm component:* Libvirt 1.2.8 introduced a regression where disk type is converted from”block” to “file” after live storage migration. This breaks the disk extensionlogic, leading to unwanted extension using all free space in the storage domain.libvirt-daemon-1.2.8-16.el7_1.1 and libvirt-python-1.2.8-6.el7_1.1 fixed thisissue by adding a new flag. RHEV-3.5.1 uses the new flag when available, fixingthis issue; however, the fix in RHEV-3.5.1 is effective only when using fixedversions of libvirt-daemon and libvirt-python.Do not perform live storage migration on block storage in RHEL 7.1 unless youhave the fixed version of libvirt-daemon (libvirt-daemon-1.2.8-16.el7_1.1) andlibvirt-python (libvirt-python-1.2.8-6.el7_1.1). These versions should beavailable as a zero-day async release with RHEL 7.1. (BZ#1196049)* After adopting Red Hat Enterprise Linux 7 and systemd, the work of preparingthe environment before the VDSM service starts was managed by systemd itselfusing the ExecStartPre API. This preparation work was implemented undervdsm_init_common.sh and included network restoration. On DHCP networks, a sideeffect of this was the spawning of a dhclient daemon by init scripts. SinceExecStartPre API prohibits long-running processes, systemd kills those processessilently, leaving hosts with no dhclient to renew their IP lease. Now, thenetwork restoration part of the preparation work is delegated to anotherdependent systemd unit resulting in a new ‘oneshot’ type service that is a vdsmddependency, called ‘vdsm-network’. Also systemd is now told not to kill dhclientprocesses upon stopping vdsm-network service. (BZ#1204782)* An unversioned hotfix of the communication protocol between the Red HatEnterprise Virtualization Manager and virtualization hosts resulted inexceptions in engine-log, and caused the Manager to be unable to communicatewith hosts. To avoid this, when using Manager to host communication via JSON-RPC(which is new in 3.5), you must update the Manager to the new version beforeupdating the virtualization hosts. Any host using JSON-RPC can only be upgradedonce the new engine release is running. Alternatively, configure the Manager touse XML-RPC instead. (BZ#1196735)* Previously, live migration of a virtual machine with an external providernetwork (OpenStack Neutron) attached failed if security groups were set, becausethe ‘vdsm-hook-openstack’ hook was not able to handle this. Now, the hook isable to handle security groups properly on source and destination hosts, andvirtual machines can be live migrated with an external provider networkattached. (BZ#1196077)* Previously, ‘hosted-engine’ called the VDSM wrapping ‘vdsClient’ utility overSSL, which caused SSL timeout errors for long sync commands. Now, the ‘vdscli’library is used instead of ‘vdsClient’, and this prevents SSL timeouts.(BZ#1190207)* Previously, when upgrading hosts from 3.4.x to 3.5.0 using ‘yum update vdsm’,VDSM was not restarted; as a result, the next time VDSM was restarted, itfailed, and manual steps had to be performed to restore the service. Now, thisissue has been resolved, and upgrading hosts from 3.4.x to 3.5.0 succeeds.Note: This issue did not apply to using the ‘Reinstall’ button in theAdministration Portal. (BZ#1208752)
Before applying this update, make sure all previously released errata relevantto your system have been applied.This update is available via the Red Hat Network. Details on how touse the Red Hat Network to apply this update are available athttps://access.redhat.com/articles/11258Red Hat Enterprise Virtualization 3

SRPMS:
vdsm-4.16.13.1-1.el6ev.src.rpm
    MD5: dc894419a9cd54e9482d72351b48792dSHA-256: a4609229974dc440aa6ec9d58c1940ffba5d76ebd60e17e873909494aeb1964f
vdsm-4.16.13.1-1.el7ev.src.rpm
    MD5: b2e7d31684015f6dc2562928b8add149SHA-256: d594766c7292bd071e6687d525d2a8e58fc3138fea16db1cfe234d0790731b17
 
x86_64:
vdsm-4.16.13.1-1.el6ev.x86_64.rpm
    MD5: e83f23f3bf20084ededa11f5d484d30eSHA-256: d29f50fcb504aad0813355f8336a3c8951af4a0a6f8fe78d3d7721fc3e9a456d
vdsm-4.16.13.1-1.el7ev.x86_64.rpm
    MD5: b2e7cfa0e3b4b667fc721af766f56d1fSHA-256: da870984d85e814d275f4c4fdc926d57453473ddaa557b57f6953dbe4cc15ae7
vdsm-bootstrap-4.16.13.1-1.el6ev.noarch.rpm
    MD5: 6fc6bcbd19a416741c8dba1c52f8c290SHA-256: 88d80abf629ed5eedda80041fe2ce0a9db31c0ea3c3bfdceb7de289cb1512454
vdsm-bootstrap-4.16.13.1-1.el7ev.noarch.rpm
    MD5: c087273259ef204a89d18288f035c2c7SHA-256: 23c672e205ce87a8ba7b6432d83c123eaa24ea5aac89e79b1a02d47730f7c249
vdsm-cli-4.16.13.1-1.el6ev.noarch.rpm
    MD5: 66db968ee7e3fd1a50e0c1fa5fa156c4SHA-256: 3896a8e3c4cef7646f89f0aa61a08aed2595a146bfa2df10a4c3527dd6be9eeb
vdsm-cli-4.16.13.1-1.el7ev.noarch.rpm
    MD5: fb486ba4587df834234bbf452f509decSHA-256: 0054181a43fecd18750fcade6142cd827e2d199ed365fad69f0ba4024dbd0eaf
vdsm-debuginfo-4.16.13.1-1.el6ev.x86_64.rpm
    MD5: 604341d0cf6dd17b73e352800359e0e1SHA-256: c72d0b1ce6878aa737446793728975c7579ac10617f0272da2e319d31e3b81e3
vdsm-hook-ethtool-options-4.16.13.1-1.el6ev.noarch.rpm
    MD5: 92b38179c4e44a567a08c9a8382d5f3aSHA-256: a698fb2b8281e6931c438637975f20382ce66d57f386b7d09da96eca235a95e4
vdsm-hook-ethtool-options-4.16.13.1-1.el7ev.noarch.rpm
    MD5: 1f570678914f9abd0701a35fcc28d111SHA-256: 58e944aa1e0f871de6c8c25dc09eaef457d40db85090acb6f5f02e8aefae36d4
vdsm-hook-macspoof-4.16.13.1-1.el6ev.noarch.rpm
    MD5: 3bf19e7547ff2eba3716dcb137a04d31SHA-256: 15ba5b2f557c060a38f26377d0963988ce49a6f4b8c889090273e8b00f57be76
vdsm-hook-macspoof-4.16.13.1-1.el7ev.noarch.rpm
    MD5: b010568c2d2d64b17cb9593886935313SHA-256: 14008a3c6e2e9cae030cd95609f6f292dddb6beda0873cd8c214a09d11ff5044
vdsm-hook-openstacknet-4.16.13.1-1.el6ev.noarch.rpm
    MD5: 918cdda1f1606e383f4d4beaab522e8fSHA-256: 40a42bd314956396b3da764bf5f10963a6a990ab697d19d433dfcd9570330ab2
vdsm-hook-openstacknet-4.16.13.1-1.el7ev.noarch.rpm
    MD5: 3e1aa68e5b3be83ad630c59ecc3e2b58SHA-256: 94c5de64e156b4c0a60c4309a7de2b9f3b9d9a64d275e97db5f9c2aaab3f78dd
vdsm-hook-vhostmd-4.16.13.1-1.el6ev.noarch.rpm
    MD5: 907f7b324aa351084f8a35db39df2564SHA-256: 975f0dd3205a92b8cf718e7ade2326216425c2e33acc434f1799105e6546e367
vdsm-hook-vhostmd-4.16.13.1-1.el7ev.noarch.rpm
    MD5: 7808c406819f8fbe0daa9390e82a876dSHA-256: 9346c31abf04562b35d11ad727d6a8a0ac1312484d227a290d4ed4520c1207bd
vdsm-jsonrpc-4.16.13.1-1.el6ev.noarch.rpm
    MD5: 7025327d3110603f9a0162ef3485a1beSHA-256: 412d0b3d2c31028af850dd1eddb5cdf9a41f49ce72120007e3b555938e7caef4
vdsm-jsonrpc-4.16.13.1-1.el7ev.noarch.rpm
    MD5: daee1fe635e41b66f2ac2fdf0aac571bSHA-256: 35f2f3b5344fee54ab6ec3227dfc7763217e44bfc23d3db42c74fc2882b9c068
vdsm-python-4.16.13.1-1.el6ev.noarch.rpm
    MD5: 57882b68c604a46a345b979fc9a67bcdSHA-256: 1344248e718532dbb93bb8e121acee010501a833f12d1a7a9cd598cd8639f623
vdsm-python-4.16.13.1-1.el7ev.noarch.rpm
    MD5: 5a4eb206b7727b1de23ed9c883dd4f4eSHA-256: 0d5c51fe3c38a4fd5103da26a5266202c64dceb019bfc182b28f72bdf2a5bd28
vdsm-python-zombiereaper-4.16.13.1-1.el6ev.noarch.rpm
    MD5: 74cb2788ae65df6fda5a4a0279ac38a0SHA-256: c50d815947471068ab0dbd02c889a2a8b34baef4d7f0c7fc8c219353c930fc98
vdsm-python-zombiereaper-4.16.13.1-1.el7ev.noarch.rpm
    MD5: 53ff145fe0842856fa99775fe9999730SHA-256: 1cb0ab3e14f91f4d958cf0b1f4a6f9c0a10a4c54a0825875531d9ac71a820079
vdsm-reg-4.16.13.1-1.el6ev.noarch.rpm
    MD5: 65ae6629bb8ccbfa3f21e165d56a098eSHA-256: f00507b65b04d17dd4a71f6a1318a15dc822cd404effd51f621cb75e6e3913aa
vdsm-reg-4.16.13.1-1.el7ev.noarch.rpm
    MD5: 59cc0320d00ba5151b6dd28831e8215cSHA-256: 3c9754015990a9d667f0b84bdbec95ed5387d6dcacb0c7e9195d62d3c37aa795
vdsm-xmlrpc-4.16.13.1-1.el6ev.noarch.rpm
    MD5: 4df9d009fe80a2408d0a6366554f36bbSHA-256: 74798a8420f27509e3427856ea811f62bed545a4cb01629dc4b59def7762c231
vdsm-xmlrpc-4.16.13.1-1.el7ev.noarch.rpm
    MD5: 4ae7dd4b7f627ececa0c00a790e3cf2aSHA-256: 61ba3b65db4bed8500e211d349bfafaea7579eca2c98d751141d148d6740f11d
vdsm-yajsonrpc-4.16.13.1-1.el6ev.noarch.rpm
    MD5: 4387b63779e05efb154fa2740a778a8fSHA-256: 9a0652182ff00ed1fd4039268daea19fc8f4dee84b6977f1e898ed24f9be567e
vdsm-yajsonrpc-4.16.13.1-1.el7ev.noarch.rpm
    MD5: 87950bc9a48510bb0dd3cbccdb0230dcSHA-256: 39bf4f896f62f9e674932c9b3702d610346e521054ba7fdcc299441fc4e82ed1
 
(The unlinked packages above are only available from the Red Hat Network)
1174813 – rhev-m stops syncing the VM statuses after massive live VM migration which fails.1178838 – iSCSI multipath fails to work and only succeed after adding configuration values for network using sysctl1190207 – vdsClient/vdscli SSLError timeout error1195113 – vdsm package causes logrotate to trigger selinux AVC alerts1195116 – Problem parsing stomp frames where trailing was cut off1196049 – [Rhel7.1] After live storage migration on block storage vdsm extends migrated drive using all free space in the vg1196735 – [performance] bad getVMList output creates unnecessary calls from Engine1199815 – Failed to auto shrink qcow block volumes on merge1199816 – Live-deleting a snapshot of preallocated disk results in a block domain using up all available space1204782 – [RHEL 7.0 + 7.1] Host configure with DHCP is losing connectivity after some time – dhclient is not running1207808 – Live Merge: Active layer merge is not properly synchronized with vdsm1208752 – Vdsm upgrade 3.4 >> 3.5.1 doesn’t restart vdsmd service1209028 – StorageDomainAccessError: Domain is either partially accessible or entirely inacessible when creating an iSCSI storage domain with RHEV-H 6.61209108 – [3.5-6.6/7.1] Failed to retrieve iscsi lun from hardware iscsi after register to RHEV-M

These packages are GPG signed by Red Hat for security. Our key and
details on how to verify the signature are available from:

Leave a Reply