[ovirt-users] Can't add host - Failed to read hardware information
David Pinkerton
dpinkert at redhat.com
Fri Oct 7 10:52:01 UTC 2016
I'm trying to add a host to a freshly built cluster.
yum install finishes, then the message " Failed to read hardware
information" is displayed - host has installation failed.
If I try to re-install I get the same message and the host goes
non-responsive.
engine log:
2016-10-07 21:13:46,525 INFO
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
[2854e702] Connecting to /192.168.21.71
2016-10-07 21:13:46,526 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
(DefaultQuartzScheduler4) [3fa97b73] Command
'GetCapabilitiesVDSCommand(HostName = rhv1,
VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
hostId='96358424-a14e-4d29-957f-3d7ddac99c12',
vds='Host[rhv1,96358424-a14e-4d29-957f-3d7ddac99c12]'})' execution failed:
org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection failed
2016-10-07 21:13:46,526 ERROR
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
(DefaultQuartzScheduler4) [3fa97b73] Failure to refresh Vds runtime info:
org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection failed
2016-10-07 21:13:46,526 ERROR
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
(DefaultQuartzScheduler4) [3fa97b73] Exception:
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection failed
at
org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.createNetworkException(VdsBrokerCommand.java:157)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:120)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:73)
[vdsbroker.jar:]
at
org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33)
[dal.jar:]
at
org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:451)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.VdsManager.refreshCapabilities(VdsManager.java:653)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring.refreshVdsRunTimeInfo(HostMonitoring.java:121)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring.refresh(HostMonitoring.java:85)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.VdsManager.onTimer(VdsManager.java:238)
[vdsbroker.jar:]
at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source)
[:1.8.0_102]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[rt.jar:1.8.0_102]
at java.lang.reflect.Method.invoke(Method.java:498)
[rt.jar:1.8.0_102]
at
org.ovirt.engine.core.utils.timer.JobWrapper.invokeMethod(JobWrapper.java:77)
[scheduler.jar:]
at
org.ovirt.engine.core.utils.timer.JobWrapper.execute(JobWrapper.java:51)
[scheduler.jar:]
at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
[quartz.jar:]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[rt.jar:1.8.0_102]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[rt.jar:1.8.0_102]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[rt.jar:1.8.0_102]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[rt.jar:1.8.0_102]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_102]
Caused by: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException:
Connection failed
at
org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient.connect(ReactorClient.java:165)
[vdsm-jsonrpc-java-client.jar:]
at
org.ovirt.vdsm.jsonrpc.client.JsonRpcClient.getClient(JsonRpcClient.java:134)
[vdsm-jsonrpc-java-client.jar:]
at
org.ovirt.vdsm.jsonrpc.client.JsonRpcClient.call(JsonRpcClient.java:81)
[vdsm-jsonrpc-java-client.jar:]
at
org.ovirt.engine.core.vdsbroker.jsonrpc.FutureMap.<init>(FutureMap.java:70)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.jsonrpc.JsonRpcVdsServer.getCapabilities(JsonRpcVdsServer.java:258)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand.executeVdsBrokerCommand(GetCapabilitiesVDSCommand.java:15)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:110)
[vdsbroker.jar:]
... 18 more
2016-10-07 21:13:49,531 INFO
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
[2854e702] Connecting to /192.168.21.71
vdsm.log
jsonrpc.Executor/3::INFO::2016-10-07
20:45:31,554::__init__::513::jsonrpc.JsonRpcServer::(_serveRequest) RPC
call Host.getCapabilities succeeded in 0.06 seconds
jsonrpc.Executor/4::DEBUG::2016-10-07
20:45:32,566::__init__::530::jsonrpc.JsonRpcServer::(_handle_request)
Calling 'Host.getHardwareInfo' in bridge with {}
jsonrpc.Executor/4::ERROR::2016-10-07
20:45:32,673::API::1340::vds::(getHardwareInfo) failed to retrieve hardware
info
Traceback (most recent call last):
File "/usr/share/vdsm/API.py", line 1337, in getHardwareInfo
hw = supervdsm.getProxy().getHardwareInfo()
File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in
__call__
return callMethod()
File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in
<lambda>
**kwargs)
File "<string>", line 2, in getHardwareInfo
File "/usr/lib64/python2.7/multiprocessing/managers.py", line 759, in
_callmethod
kind, result = conn.recv()
EOFError
jsonrpc.Executor/4::INFO::2016-10-07
20:45:32,680::__init__::513::jsonrpc.JsonRpcServer::(_serveRequest) RPC
call Host.getHardwareInfo failed (error 57) in 0.11 seconds
jsonrpc.Executor/6::DEBUG::2016-10-07
20:45:33,783::__init__::530::jsonrpc.JsonRpcServer::(_handle_request)
Calling 'Host.getCapabilities' in bridge with {}
MainThread::DEBUG::2016-10-07 20:45:36,211::vdsm::73::vds::(sigtermHandler)
Received signal 15
I'm also seeing segfaults in supervdsm on the host's console.
--
David Pinkerton
+61-488-904-232
<http://apac.redhat.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20161007/8ee39938/attachment-0001.html>
More information about the Users
mailing list