Description of problem:
The intent of this bug is just to point out a problem that happened recently and that it is currently being addressed via a kernel bug, BZ 1081282.
The problem is that the 'sudo' command hung in getifaddrs().
For the customer that encountered this, when they started VDSM, the supervdsm process failed to start due to 'sudo' hanging and VDSM was therefore unable to connect to supervdsm's socket. The host then became Non-Responsive.
Version-Release number of selected component (if applicable):
RHEL 6.5 hosts with 'vdsm-4.13.2-0.11'
It only happened the one time.
Steps to Reproduce:
BZ1081282 is related to RHEL6. ovirt/rhevm 3.6.x won't support RHEL6 as hosts.
vdsm requires kernel >= 3.10.0-132.el7, although BZ1081282 doesn't mention anything about RHEL7 kernel...
Please put valid keyword so it's clear it doesn't require any QA action. Thank you.
# yum deplist vdsm | grep 'dependency.*kernel'
dependency: kernel >= 3.10.0-132.el7
# yum info vdsm | egrep "^Release|^Version"
Version : 4.17.0
Release : 1054.git562e711.el7
Please notice this bug is also dependant on BZ#1092400 which is rhel7.
so I think there's no need in adding a flag.
ok, vdsm-4.17.0-1198.git6ede99a.el7.noarch / 3.6.0-4 (no issue found)
# rpm -qRp http://bob.eng.lab.tlv.redhat.com/builds/3.6/3.6.0/3.6.0-4/snapshot/rpm/el7Server/noarch/vdsm-4.17.0-1198.git6ede99a.el7.noarch.rpm | grep ^kernel
kernel >= 3.10.0-132.el7
# rpm -q kernel
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.