[00:39] <mup> Bug #1524502 changed: [xenial, 1.10] dhcpd.conf doesn't get created anymore <python3> <MAAS:New> <https://launchpad.net/bugs/1524502>
[00:54] <mup> Bug #1524563 opened: [1.10] Importing boot images on the cluster fails <python3> <MAAS:Triaged by blake-rouse> <https://launchpad.net/bugs/1524563>
[01:00] <mup> Bug #1524563 changed: [1.10] Importing boot images on the cluster fails <python3> <MAAS:Triaged by blake-rouse> <https://launchpad.net/bugs/1524563>
[01:06] <mup> Bug #1524563 opened: [1.10] Importing boot images on the cluster fails <python3> <MAAS:Triaged by blake-rouse> <https://launchpad.net/bugs/1524563>
[14:23] <mup> Bug #1524853 opened: DHCP lease allocation does not match deployed node's IP address <MAAS:New> <https://launchpad.net/bugs/1524853>
[14:26] <mup> Bug #1524853 changed: DHCP lease allocation does not match deployed node's IP address <MAAS:New> <https://launchpad.net/bugs/1524853>
[14:32] <mup> Bug #1524853 opened: DHCP lease allocation does not match deployed node's IP address <MAAS:Triaged> <https://launchpad.net/bugs/1524853>
[15:44] <mup> Bug #1524881 opened: [xenial,1.10] enlistment failure  <python3> <MAAS:New> <https://launchpad.net/bugs/1524881>
[15:44] <mup> Bug #1524883 opened: [xenial,1.10] Can't Add Chassis <python3> <MAAS:New> <https://launchpad.net/bugs/1524883>
[15:47] <mup> Bug #1524881 changed: [xenial,1.10] enlistment failure  <python3> <MAAS:New> <https://launchpad.net/bugs/1524881>
[15:47] <mup> Bug #1524883 changed: [xenial,1.10] Can't Add Chassis <python3> <MAAS:New> <https://launchpad.net/bugs/1524883>
[15:53] <mup> Bug #1524881 opened: [xenial,1.10] enlistment failure  <python3> <MAAS:New> <https://launchpad.net/bugs/1524881>
[15:53] <mup> Bug #1524883 opened: [xenial,1.10] Can't Add Chassis <python3> <MAAS:New> <https://launchpad.net/bugs/1524883>
[18:03] <mup> Bug #1524924 opened: maas does not enable all interfaces during commisoning <MAAS:New> <https://launchpad.net/bugs/1524924>
[18:03] <mup> Bug #1524925 opened: Auto-enlist not working for power8 <MAAS:New> <https://launchpad.net/bugs/1524925>
[20:05] <mwenning> hi guys, I tried maas maas node start <system-id>  and got back "can't start node: it hasn't been allocated".  All nodes were in ready state.   Am I missing something?
[20:06] <mwenning> ^^ maas 1.8.2
[20:18] <mup> Bug #1524954 opened: Curtin error when deploying a maas/juju environment <MAAS:New> <https://launchpad.net/bugs/1524954>
[20:24] <mup> Bug #1524954 changed: Curtin error when deploying a maas/juju environment <MAAS:New> <https://launchpad.net/bugs/1524954>
[20:36] <mup> Bug #1524954 opened: Curtin error when deploying a maas/juju environment <curtin:New> <https://launchpad.net/bugs/1524954>
[20:39] <mup> Bug #1524954 changed: Curtin error when deploying a maas/juju environment <curtin:New> <https://launchpad.net/bugs/1524954>
[20:42] <mup> Bug #1524954 opened: Curtin error when deploying a maas/juju environment <curtin:New> <https://launchpad.net/bugs/1524954>
[20:45] <mup> Bug #1524954 changed: Curtin error when deploying a maas/juju environment <MAAS:New> <https://launchpad.net/bugs/1524954>
[21:30] <nodtkn> howdy!  Is there an easy way to to tell curtin not got grow the root partition to the entire disk or do I need to override builtin in partition_commands in curtin_userdata?
[22:27] <mup> Bug #1524995 opened: [xenial, 1.10] Error on enlistment start <python3> <MAAS:Triaged> <https://launchpad.net/bugs/1524995>