[06:20] <mup> Bug #1589140 opened: No WOL option in latest MAAS version for 16.04 also the Manual settings crashes <MAAS:Confirmed> <https://launchpad.net/bugs/1589140>
[06:36] <reikermann> Hi, my MAAS hardware test stress-ng-cpu-long is getting a timed out error after 11:59:26 , but the test definition is a 12h test why is the timeout so short?
[07:53] <mup> Bug #1710092 opened: Hardware Tests have a short timeout  <MAAS:New> <https://launchpad.net/bugs/1710092>
[07:53] <mup> Bug #1710096 opened: [2.2] for non-local network ranges, allow_proxy should be false by default <MAAS:New> <https://launchpad.net/bugs/1710096>
[10:57] <D4RKS1D3> bryan_att, you have the curtin documentation
[10:58] <D4RKS1D3> let me share with you the link
[10:58] <D4RKS1D3> bryan_att, https://media.readthedocs.org/pdf/curtin/latest/curtin.pdf
[13:23] <mup> Bug #1710177 opened: curtin in-target commands do not work for ubuntu core <MAAS:New> <https://launchpad.net/bugs/1710177>
[14:16] <bryan_att> D4RKS1D3: many thanks, just what I was looking for. I'm trying to find out how to circumvent the cloud-init/NIC race condition that resulted in the DEVTIMEOUT option being added, so I can avoid the 5-min hang due to the primary NIC not being ready in time.
[14:17] <bryan_att> e.g. per https://bugzilla.redhat.com/show_bug.cgi?id=1194623 and https://lists.stg.fedoraproject.org/archives/list/spins@lists.stg.fedoraproject.org/thread/2OYS7FSN6WUFBF7CQG4STCR73K72QUPK/  - I think that is what I am encountering.
[15:22] <bryan_att> anyone familiar with how to format the kernel options that MAAS allows: can you tell me if the format at http://cloudinit.readthedocs.io/en/latest/topics/network-config.html for disabling network configuration (network-config={config: disabled}) is correct for use in MAAS?
[15:23] <bryan_att> I am trying to see if disabling the cloud-init network config can help me avoid the NIC ready race condition that causes a 5-min delay in server bootup
[15:32] <mup> Bug #1710241 opened: Cannot deploy customized ubuntu cloud image <MAAS:New> <https://launchpad.net/bugs/1710241>
[15:44] <mup> Bug #1710241 changed: Cannot deploy customized ubuntu cloud image <MAAS:New> <https://launchpad.net/bugs/1710241>
[15:48] <mup> Bug #1710241 opened: Cannot deploy customized ubuntu cloud image <MAAS:New> <https://launchpad.net/bugs/1710241>
[16:56] <maticue> hi everyone! one question, if I add a new Bare Metal to my network and I boot it at first time with PXE, MAAS will discover it. My question is, at that stage is it possible to execute directly the commissioning stage automatically?
[17:00] <maticue> I'm trying to identify automatically IPMI
[17:00] <maticue> for each bare metal
[19:42] <mup> Bug #1710278 opened: [2.3a1] named stuck on reload, DNS broken <MAAS:New> <https://launchpad.net/bugs/1710278>
[20:06] <blizzow> I have three machines that maas has enlisted.  I changed the hostnames/entered their IPMI information and selected all of them to be commissioned.  They all show the RAM and CPU core after being commissioned, but there are no disks detected. What do I have to do to get the disks detected and do a deployment?