[00:28] <pmatulis> gottaloveit, what shows up on the client screen when it PXE boots?
[00:44] <ytc> ?
[00:44] <ytc> ls
[01:03] <gottaloveit> 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] <pmatulis> gottaloveit, sounds like the node does not have internet access
[01:11] <pmatulis> gottaloveit, you may need to set up ip masquerading somewhere, probably on the maas api server
[01:11] <gottaloveit> 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] <pmatulis> gottaloveit, i assume you're running 2.1
[01:22] <gottaloveit> 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] <gottaloveit> 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] <gottaloveit> ?
[02:22] <pmatulis> gottaloveit, click on a subnet
[20:01] <mup> Bug #1646571 opened: apt failures non fatal, but cloud the log <landscape> <cloud-init:New> <MAAS:New> <https://launchpad.net/bugs/1646571>