[09:20] <BlackDex> What is the best way to backup MaaS?
[13:04] <mup> Bug #1553176 opened: BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload <BIND:New> <MAAS:New> <bind9 (Ubuntu):Confirmed> <https://launchpad.net/bugs/1553176>
[13:35] <narindergupta> roaksoax: hi current MAAS 1.9 failed the deployment of Xenial due to cloud init issue? Is this something known issue?
=== nagyz is now known as angyz
=== angyz is now known as nagyz
[14:42] <smoser> lets do try to not just always blame cloud-init for everything.
[14:43] <roaksoax> smoser: well, for any normal user who sees the output it would appear that that's the case
[15:20] <mag009__> is it to select a specific image when deploying
[15:20] <mag009__> from the api
[15:20] <mag009__> 1.0
[15:31] <mag009__> actually my question is can we deploy from the api
[15:32] <mag009__> /api/2.0/machines/{system_id}/ op=deploy alright got my answer
[15:32] <mag009__> its only available with api 2.0
[15:37] <mag009__> now the question is where can I activate api 2.0 on a xenial server?
[15:38] <mag009__> I got the following version of maas 1.10.0+bzr4578-0ubuntu2
[16:23] <mup> Bug #1553261 opened: [FFe] Standing FFe for MAAS 2.0 <maas (Ubuntu):New> <https://launchpad.net/bugs/1553261>
=== redelmann is now known as rudi|comida
[17:08] <mup> Bug #1550616 changed: API 2.0 cleanup <MAAS:Fix Released by ltrager> <https://launchpad.net/bugs/1550616>
[17:17] <mup> Bug #1550616 opened: API 2.0 cleanup <MAAS:Fix Released by ltrager> <https://launchpad.net/bugs/1550616>
[17:23] <mup> Bug #1550616 changed: API 2.0 cleanup <MAAS:Fix Released by ltrager> <https://launchpad.net/bugs/1550616>
=== rudi|comida is now known as redelmann
[18:11] <mup> Bug #1553288 opened: json.decoder.JSONDecodeError: Expecting property name enclosed in double quotes: line 1 column 2 (char 1) <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1553288>
[18:29] <mup> Bug #1553297 opened: The commission action for 1 node failed with error: 'NoneType' object has no attribute 'id' <MAAS:New> <https://launchpad.net/bugs/1553297>
[18:29] <mup> Bug #1553301 opened: [2.0a1] After upgrade from 1.10, enabloing dhcp fails <MAAS:New> <https://launchpad.net/bugs/1553301>
=== ejat_ is now known as ejat
[20:00] <LiftedKilt> quick question if anyone has a moment: attempting to deploy maas, and only half of my servers are coming up
[20:00] <LiftedKilt> they are all identical hardware, identical port configuration (on the same switch)
[20:01] <LiftedKilt> they pxe boot, and they all finish with generating ssh keys and identifying themselves as node-##.domain.tld
[20:41] <mup> Bug #1553352 opened: [2.0] is_pid_in_container is not checking correctly <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1553352>
[20:44] <mup> Bug #1553352 changed: [2.0] is_pid_in_container is not checking correctly <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1553352>
[20:53] <mup> Bug #1553352 opened: [2.0] is_pid_in_container is not checking correctly <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1553352>