[ovirt-users] hosted-engine --deploy stalls on "Waiting for VDSM hardware info"

[Alex Harpin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

I've been running oVirt 3.6 on Fedora 22 for a while now, as a two
node set up, and everything was going fine until I decided to upgrade
from Fedora 22 to 23 (as 22 is pretty much EOL). That didn't go
exactly to plan, so to minimise any issues moving forward I did a
complete new install of Fedora 23 on one of the hosts, with a view to
just importing the back up from the 3.6 system.

The issue I'm running into at the moment is that when I run
hosted-engine --deploy (hosted engine setup obviously) on the new
host, the process gets to "Waiting for VDSM hardware info", repeats
that for a while and then fails out of the set up.

I've pinned it down to the following not returning the expected
information:

vdsClient -s 0 getVdsHardwareInfo

This returns "Failed to read hardware information" rather than the
expected information.

Running this same command on the Fedora 22 system returns hardware
information, even installing 3.6 on the new system returns the same
error. I'm presuming it's not a specific oVirt issue, but down to
some dmidecode (or related) issue.

Running the above, rather than hosted-engine --deploy gives the
following as the last entry in supervdsm.log

MainProcess|jsonrpc.Executor/2::DEBUG::2016-07-08
08:08:04,377::supervdsmServer::92::SuperVdsm.ServerCallback::(wrapper)
call getHardwareInfo with () {}
MainProcess|jsonrpc.Executor/2::ERROR::2016-07-08
08:08:04,409::supervdsmServer::96::SuperVdsm.ServerCallback::(wrapper)
Error in getHardwareInfo
Traceback (most recent call last):
File "/usr/share/vdsm/supervdsmServer", line 94, in wrapper
res = func(*args, **kwargs)
File "/usr/share/vdsm/supervdsm_api/hwinfo.py", line 29, in
getHardwareInfo
return getHardwareInfoStructure()
File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 465, in
__call__
value = self.func(*args)
File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line
52, in getHardwareInfoStructure
dmiInfo = getAllDmidecodeInfo()
File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 465, in
__call__
value = self.func(*args)
File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line
46, in getAllDmidecodeInfo
myLeafDict[k] = __leafDict(getattr(dmidecode, k)())
File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line
34, in __leafDict
ret.update(__leafDict(v))
File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line
34, in __leafDict
ret.update(__leafDict(v))
File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line
32, in __leafDict
for k, v in d.iteritems():
IndexError: list assignment index out of range

Running dmidecode manually appears to return the same information an
almost identical system returns (Dell R710).

Any pointers on tracking down what the issue might be as I'd rather
not reinstall with 22 again just to get this up and running.

Regards

Alex.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXf1RmAAoJELTttCQtz/9DV1wP/3v1144zI2cSayvhPIw67bKO
p2+CBx56ZBfOp4mYH6+oJ9/G+HxPfXWoOGICq6QiUmj7vg7aKKgsFO2hx8w6FLuH
xG22dQhcEQdTA9i0zHHhi+eLdROfeuFU93Gl59NiXVA9bglMYY6TH/Ljx+rIGyx0
DHbn4gzjkXdLFAjJj212xWEp4EU+xjG78qmk1eeLibxdGtPcsIbTKAdsvl5/Z4WL
x+poGegMb+IbwaP7co2y8Fbr0TycPSuYb7bw91jsYJmP4O/X9845bZH3JjPvAfco
uBY5/2puyZ084cr70Bpp+l4W1bQ4W4htqg/oUJATo028FeLipCqzumfGz3Ja4DPa
Nzi+VxRQssmewr0/tjidgGIiAiz+wuheuYwf687yp97WMQ0HBxOj3Kxo9JykjrnJ
Ga52GUx7CQuxnGdDUZZZw2je0Ysp87jJqX7wvTi2o+eRhnH2wfsS4PtxsIktN5nx
MgRISrhOW3+INHe8Wyl2/miw+FvRNc+EtLwJC5WQr5W3vsRINRTj4erUC8V5PpSL
vQFhFGtDjeI9rTQ7y+nvwYWGWQetERTuMwHLgMgwM4hVZq4eW4/2KI3jrcT64ZIK
Z5mcyoZBIQW4t2GaGGU8+Hw0PQw83NEHvNDZm5PMIDjVWjbuPe7ge4vDgC8Qbnxa
Lw9AV/RDnJyoEMIZhQTD
=NoZW
-----END PGP SIGNATURE-----