[09:12] <mup> Bug #1742893 opened: PXE boot fails [rackd.log - Resource temporarily unavailable] <MAAS:New> <https://launchpad.net/bugs/1742893>
[09:57] <PTO> What is wrong when a maas controller suddenly decides not to start the dhcp service with the following error: "maas-controller dhcpd[1786]: Can't open /var/lib/maas/dhcpd.conf: Permission denied"
[15:01] <mup> Bug #1713556 opened: pods: MAAS created VMs don't log console output <cdoqa> <MAAS:New> <https://launchpad.net/bugs/1713556>
[15:27] <Bob___> Hello.  I have a Curtin issue.....
[15:28] <Bob___> When I run tasks they do not run in the same order
[15:28] <Bob___> Is there anyone that can give some ideas
[15:55] <mup> Bug #1742971 opened: pod created vm fails commissioning after apparently booting to linux <cdo-qa> <cdo-qa-blocker> <foundations-engine> <cloud-init:New> <MAAS:New> <https://launchpad.net/bugs/1742971>
[17:40] <mup> Bug #1743005 opened: MAAS enlistment fails when region is behind a NAT <MAAS:New> <https://launchpad.net/bugs/1743005>
[17:49] <mup> Bug #1743005 changed: MAAS enlistment fails when region is behind a NAT <MAAS:New> <https://launchpad.net/bugs/1743005>
[17:58] <mup> Bug #1743005 opened: MAAS enlistment fails when region is behind a NAT <MAAS:New> <https://launchpad.net/bugs/1743005>
[18:49] <mup> Bug #1742324 changed: Bionic kernel panics in the MAAS ephemeral environment <bionic> <kernel-key> <MAAS:Won't Fix> <linux (Ubuntu):Triaged> <https://launchpad.net/bugs/1742324>
[19:01] <mup> Bug #1742324 opened: Bionic kernel panics in the MAAS ephemeral environment <bionic> <kernel-key> <MAAS:Won't Fix> <linux (Ubuntu):Triaged> <https://launchpad.net/bugs/1742324>
[19:10] <mup> Bug #1742324 changed: Bionic kernel panics in the MAAS ephemeral environment <bionic> <kernel-key> <MAAS:Won't Fix> <linux (Ubuntu):Triaged> <https://launchpad.net/bugs/1742324>
[20:43] <ahasenack> hi, I'm trying to enlist a node with maas 2.3.0 on xenial
[20:43] <ahasenack> it boots, gets an ip, kernel,
[20:43] <ahasenack> eventually gets to the ubuntu login prompt
[20:43] <ahasenack> and just stays there
[20:43] <ahasenack> it also doesn't show up in the nodes list with one of the petnames
[20:43] <ahasenack> no clue what it is doing
[20:43] <ahasenack> last output before the prompt is
[20:43] <ahasenack> [   12.937922] systemd-journald[472]: Received request to flush runtime journal from PID 1
[20:44] <ahasenack> it's odd because it then stays a long-ish time there, until the prompt finally shows up
[20:44] <ahasenack> by long-ish I mean maybe 2 minutes