<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 15, 2018 at 1:08 AM, Jamie Lawrence <span dir="ltr"><<a href="mailto:jlawrence@squaretrade.com" target="_blank">jlawrence@squaretrade.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> On Feb 14, 2018, at 1:27 AM, Simone Tiraboschi <<a href="mailto:stirabos@redhat.com">stirabos@redhat.com</a>> wrote:<br>
> On Wed, Feb 14, 2018 at 2:11 AM, Jamie Lawrence <<a href="mailto:jlawrence@squaretrade.com">jlawrence@squaretrade.com</a>> wrote:<br>
> Hello,<br>
><br>
> I'm seeing the hosted engine install fail on an Ansible playbook step. Log below. I tried looking at the file specified for retry, below (/usr/share/ovirt-hosted-<wbr>engine-setup/ansible/<wbr>bootstrap_local_vm.retry); it contains the word, 'localhost'.<br>
><br>
> The log below didn't contain anything I could see that was actionable; given that it was an ansible error, I hunted down the config and enabled logging. On this run the error was different - the installer log was the same, but the reported error (from the installer changed).<br>
><br>
> The first time, the installer said:<br>
><br>
> [ INFO ] TASK [Wait for the host to become non operational]<br>
> [ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts": {"ovirt_hosts": []}, "attempts": 150, "changed": false}<br>
> [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook<br>
> [ INFO ] Stage: Clean up<br>
><br>
> 'localhost' here is not an issue by itself: the playbook is executed on the host against the same host over a local connection so localhost is absolutely fine there.<br>
><br>
> Maybe you hit this one:<br>
> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1540451" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=1540451</a><br>
<br>
</span>That seems likely.<br></blockquote><div><br></div><div>At the point the engine VM is up but you can reach it only from that host since it's on a natted network.</div><div>I'd suggest to connect to the engine VM from there and check host-deploy logs.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
<br>
> It seams NetworkManager related but still not that clear.<br>
> Stopping NetworkManager and starting network before the deployment seams to help.<br>
<br>
</span>Tried this, got the same results.<br>
<br>
[snip]<br>
<span class="">> Anyone see what is wrong here?<br>
><br>
> This is absolutely fine.<br>
> The new ansible based flow (also called node zero) uses an engine running on a local virtual machine to bootstrap the system.<br>
> The bootstrap local VM runs over libvirt default natted network with its own dhcp instance, that's why we are consuming it.<br>
> The locally running engine will create a target virtual machine on the shared storage and that one will be instead configured as you specified.<br>
<br>
</span>Thanks for the context - that's useful, and presumably explains why 192.168 addresses (which we don't use) are appearing in the logs.<br>
<br>
Not being entirely sure where to go from here, I guess I'll spend the evening figuring out ansible-ese in order to try to figure out why it is blowing chunks.<br>
<br>
Thanks for the note.<br>
<span class="HOEnZb"><font color="#888888"><br>
-j</font></span></blockquote></div><br></div></div>