[00:28] gottaloveit, what shows up on the client screen when it PXE boots? [00:44] ? [00:44] ls [01:03] sorry for delay... so it pxe boots to ubuntu login, then about 30-60 seconds later a bunch of stuff flashes over, mostly errors in cloudinit, then powers off. I checked the box in MAAS to not power off and I was able to login to the client and put the /tmp/block-poweroff and neither would prevent the auto poweroff. The messages I was able to see were mostly things like "couldn't find package (chef, puppet, mcollective)" [01:10] gottaloveit, sounds like the node does not have internet access [01:11] gottaloveit, you may need to set up ip masquerading somewhere, probably on the maas api server [01:11] it is.. and i would be able to troubleshoot it, if the thing wouldn't keep automatically shutting off. why would it not listen to the /tmp/block-poweroff and the "allow ssh and keep power on" setting ? [01:21] gottaloveit, i assume you're running 2.1 [01:22] i think i found it, digging it way down deep in my iptables-restore, i noticed a 1 digit typo on ethernet device for the NAT filter. reloading/rebooting and testing in a few mins. [02:11] ok that was one of the issues, the other being, once i logged into the client using the backdoor user, I notice the /etc/resolv.conf has an IP for the DNS that I have no idea how it got there. It's not a DNS server. The file says it was auto generated via cloudinit. Does anyone know where on the MAAS API server that file would be for me to update correctly/ [02:11] ? [02:22] gottaloveit, click on a subnet === frankban|afk is now known as frankban === wolverin_ is now known as wolverineav_ === mup_ is now known as mup === jamespag` is now known as jamespage === frankban is now known as frankban|afk === frankban|afk is now known as frankban === iggy_ is now known as iggy === frankban is now known as frankban|afk [20:01] Bug #1646571 opened: apt failures non fatal, but cloud the log