RHBA-2014:1152 - Bug Fix Advisory

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 Enterprise Virtualization
Manager agent on Red Hat Enterprise Virtualization Hypervisor or Red Hat
Enterprise Linux hosts.

Changes to the vdsm component:

• Previously, when attempting to add a Red Hat Enterprise Linux 7 host to the

Manager for the first time following clean RHEL 7 installation, Vdsm failed to
start on the host, and thus the host failed to add. This happened because the
multipathd service behaves differently in RHEL 7 from how it behaves in RHEL
6.5. In RHEL 6.5, the multipathd service disables all devices when starting if
the multipath configuration file does not exist. Creating a new multipath.conf
file and reloading the multipathd service causes multipathd to reload the new
configuration, and installation can continue. In RHEL 7, under the same
circumstances, the multipathd service behaved differently, and would stop
silently, without any error. Reloading the multipathd service failed, because
the service was not running. Now, the behavior in RHEL 7 has been modified to
simulate that of multipathd on RHEL 6.5 hosts; if the multipath configuration
file is missing, the install script creates a new multipath configuration file,
and Vdsm successfully reloads the multipathd service during startup.
(BZ#1125178)

• Previously, duplicate entries were being created in /etc/logroate.d/libvirtd,

because the logs were not being rotated correctly. Now, previous content is
backed up prior to a new entry being added, and libvirt logs are rotated
successfully. (BZ#1115997)

• When a Red Hat Enterprise Virtualization Hypervisor is disconnected from the

network, resources become unavailable, virtual machines lose connectivity, and
in some cases, the host is fenced and data is lost. Previously, there was no way
to track when and why this happened. Now, a new log at
/var/log/vdsm/connectivity.log allows administrators to track network
connectivity. The log tracks the reported speed and duplex of host network
interfaces, and when Vdsm's client (most commonly, Engine) has contacted Vdsm.
(BZ#1122010)

• Previously, if sanlock was present on a system during upgrade from version 3.3

to 3.4, the system attempted to stop and restart sanlock. The update process
would finish, but with vdsm-tool exceptions. Now, sanlock restart is requested
by vdsm-tool only if there is a relevant change. (BZ#1088805)

All users managing Red Hat Enterprise Linux Virtualization hosts using Red Hat
Enterprise Virtualization Manager are advised to install these updated packages.

Solution

Before applying this update, make sure all previously released errata relevant
to your system have been applied.

This update is available via the Red Hat Network. Details on how to use the Red
Hat Network to apply this update are available at
https://access.redhat.com/site/articles/11258

Affected Products

• Red Hat Virtualization 3.4 x86_64
• Red Hat Virtualization 3 for RHEL 7 x86_64
• Red Hat Virtualization 3 for RHEL 6 x86_64

Fixes

• BZ - 1088805 - Appear vdsm-tool exception in time of vdsm package upgrade from 3.3 to 3.4
• BZ - 1115997 - "/etc/logrotate.d/libvirtd" file is having multiple entries of "/var/log/libvirt/libvirtd.log" after upgrading the host to "rhev-hypervisor6-6.5-20140603.2" version.
• BZ - 1119060 - Pthreading is imported too late
• BZ - 1122010 - [RFE] Host Self-Health Log: network connectivity information
• BZ - 1123842 - Can't login the hypervisor with correct password after upgrading the RHEV-H from "rhevh-6.5-20140603.2.el6ev.iso" to "rhevh-6.5-20140618.0.el6ev.iso"
• BZ - 1125178 - multipathd reload fails when installing running vdsm in the first time on a fresh install where multipath.conf is missing

CVEs

(none)

References

(none)