Re: [ovirt-users] Failed to read hardware information

On Mon, Oct 10, 2016 at 5:05 AM, Charles Kozler <ckozleriii(a)gmail.com&gt; wrote: > Possibly stupid question but are you doing this on a base empty > centos/rhel 7? > > On Oct 9, 2016 9:48 PM, "David Pinkerton" <dpinkert(a)redhat.com&gt; wrote: > >> >> I've spent the weekend trying to get to the bottom of this issue. >> >> Adding a Host fails: >> >> From RHVM >> >> >> VDSM rhv1 command failed: Connection reset by peer >> Could not get hardware information for host rhv1 >> VDSM rhv1 command failed: Failed to read hardware information >> Host rhv1 installed >> Network changes were saved on host rhv1 >> Installing Host rhv1. Stage: Termination. >> Installing Host rhv1. Retrieving installation logs to: >> '/var/log/ovirt-engine/host-deploy/ovirt-host-deploy-2016101 >> 0115606-192.168.21.71-24d39274.log'. >> Installing Host rhv1. Stage: Pre-termination. >> Installing Host rhv1. Starting ovirt-vmconsole-host-sshd. >> Installing Host rhv1. Starting vdsm. >> Installing Host rhv1. Stopping libvirtd. >> Installing Host rhv1. Stage: Closing up. >> Installing Host rhv1. Setting kernel arguments. >> Installing Host rhv1. Stage: Transaction commit. >> Installing Host rhv1. Enrolling serial console certificate. >> Installing Host rhv1. Enrolling certificate. >> Installing Host rhv1. Stage: Misc configuration. >> >> >> >> This was in the /var/log/vdsm/vdsm.log on the host trying to be added: >> >> jsonrpc.Executor/2::ERROR::2016-10-10 11:57:10,276::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 >> > If a request to supervdsm fails with EOFError, something bad happened supervdsm and we would see the exception in the supervdsm log. Can you share supervdsm.log? Nir