<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Oct 10, 2016 at 5:05 AM, Charles Kozler <span dir="ltr"><<a href="mailto:ckozleriii@gmail.com" target="_blank">ckozleriii@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><p dir="ltr">Possibly stupid question but are you doing this on a base empty centos/rhel 7?</p>
<div class="gmail_extra"><br><div class="gmail_quote"><div><div class="gmail-h5">On Oct 9, 2016 9:48 PM, "David Pinkerton" <<a href="mailto:dpinkert@redhat.com" target="_blank">dpinkert@redhat.com</a>> wrote:<br type="attribution"></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="gmail-h5"><div dir="ltr"><br>I've spent the weekend trying to get to the bottom of this issue.<br><br>Adding a Host fails:<br><br>From RHVM<br><br><br>VDSM rhv1 command failed: Connection reset by peer<br>Could not get hardware information for host rhv1<br>VDSM rhv1 command failed: Failed to read hardware information<br>Host rhv1 installed<br>Network changes were saved on host rhv1<br>Installing Host rhv1. Stage: Termination.<br>Installing Host rhv1. Retrieving installation logs to: '/var/log/ovirt-engine/host-de<wbr>ploy/ovirt-host-deploy-2016101<wbr>0115606-192.168.21.71-24d39274<wbr>.log'.<br>Installing Host rhv1. Stage: Pre-termination.<br>Installing Host rhv1. Starting ovirt-vmconsole-host-sshd.<br>Installing Host rhv1. Starting vdsm.<br>Installing Host rhv1. Stopping libvirtd.<br>Installing Host rhv1. Stage: Closing up.<br>Installing Host rhv1. Setting kernel arguments.<br>Installing Host rhv1. Stage: Transaction commit.<br>Installing Host rhv1. Enrolling serial console certificate.<br>Installing Host rhv1. Enrolling certificate.<br>Installing Host rhv1. Stage: Misc configuration.<br><br><br><br>This was in the /var/log/vdsm/vdsm.log on the host trying to be added:<br><br>jsonrpc.Executor/2::ERROR::201<wbr>6-10-10 11:57:10,276::API::1340::vds::<wbr>(getHardwareInfo) failed to retrieve hardware info<br>Traceback (most recent call last):<br> File "/usr/share/vdsm/API.py", line 1337, in getHardwareInfo<br> hw = supervdsm.getProxy().getHardwa<wbr>reInfo()<br> File "/usr/lib/python2.7/site-packa<wbr>ges/vdsm/supervdsm.py", line 53, in __call__<br> return callMethod()<br> File "/usr/lib/python2.7/site-packa<wbr>ges/vdsm/supervdsm.py", line 51, in <lambda><br> **kwargs)<br> File "<string>", line 2, in getHardwareInfo<br> File "/usr/lib64/python2.7/multipro<wbr>cessing/managers.py", line 759, in _callmethod<br> kind, result = conn.recv()<br>EOFError<br></div></div></div></blockquote></div></div></blockquote><div><br></div><div>If a request to supervdsm fails with EOFError, something bad happened</div><div>supervdsm and we would see the exception in the supervdsm log.</div><div><br></div><div><div>Can you share supervdsm.log?</div></div><div><br></div><div>Nir</div></div></div></div>