<div dir="auto">Hey wahi,<div dir="auto"><br></div><div dir="auto">To access the deployed machine, go to the maas UI , select "settings" in the upper right.</div><div dir="auto"><br></div><div dir="auto">At the top you will see a section to add your ssh key. Make sure you do so, you can either import a key via launchpad or add one from a local system. </div><div dir="auto"><br></div><div dir="auto">After doing so, click back on your "nodes" tab and release & deploy the kvm instance again. You should be able to ssh into the machine once it comes up again. </div><div dir="auto"><br></div><div dir="auto">To find what the IP is, simply click on your "networks" tab or you can watch the VM console.</div><div dir="auto"><br></div><div dir="auto">-sfeole</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Jul 21, 2017 4:18 AM, "wahi" <<a href="mailto:wahi@sci.am">wahi@sci.am</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Hi Mike,</p>
<p>Actually Lloyd suggestion was rigth, the issue was from the
iptables, I opened the 5240 port and it worked. The interesting
question is, what is the default username and password for KVM PXE
VM (Ubuntu 16.04)</p>
<p><br>
</p>
<p>Best,</p>
<p> Wahi<br>
</p>
<br>
<div class="m_6906434046821502458moz-cite-prefix">On 07/21/2017 10:58 AM, Mike Pontillo
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Fri, Jul 21, 2017 at 7:36 AM, wahi
<span dir="ltr"><<a href="mailto:wahi@sci.am" target="_blank">wahi@sci.am</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">On 07/20/2017 10:56 PM,
Lloyd Parkes wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The error message
indicates that the VM couldn’t download its bootstrap
from the server using the TFTP protocol. The TFTP
protocol isn’t used when installing from an ISO.<br>
<br>
I can think of two things to check.<br>
<br>
First of all, got to Nodes -> Controllers and select
your rack controller. Then select the Services tab and
check that there is a green tick next to the “tftp”
item. If there isn’t a green tick, then you will have to
search the MAAS logs under /var/log/maas/ for possible
problems.<br>
<br>
Secondly, there is always the possibility of a firewall
blocking tftp traffic. This could be on your server or
on your network.<br>
</blockquote>
</blockquote>
<div><br>
</div>
<div>In addition to Lloyd's suggestions, you can try using
this script for testing:</div>
<div><br>
</div>
<div><a href="https://git.launchpad.net/maas/tree/scripts/maas-test-enlistment" target="_blank">https://git.launchpad.net/<wbr>maas/tree/scripts/maas-test-<wbr>enlistment</a><br>
</div>
<div><br>
</div>
<div>If you run this script manually from the same network
as the nodes are booting from (using the private IP
address, <span style="font-size:12.8px">10.0.17.1, as the
parameter) you should be able to check that the TFTP
files are accessible and the cloud parameters are
correct (that is, the MAAS metadata server that
cloud-init will contact is reachable and providing
correct metadata URLs for booting nodes).</span></div>
<div><span style="font-size:12.8px"><br>
</span></div>
<div><span style="font-size:12.8px">Regards,</span></div>
<div><span style="font-size:12.8px">Mike</span></div>
</div>
</div>
</div>
</blockquote>
<br>
<pre class="m_6906434046821502458moz-signature" cols="72">
</pre>
</div>
<br>--<br>
Maas-devel mailing list<br>
<a href="mailto:Maas-devel@lists.ubuntu.com">Maas-devel@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/maas-devel" rel="noreferrer" target="_blank">https://lists.ubuntu.com/<wbr>mailman/listinfo/maas-devel</a><br>
<br></blockquote></div></div>