[04:34] <mup> Bug #1707562 opened: [2.2] no way to specify testing_scripts on machine creation <MAAS:New> <https://launchpad.net/bugs/1707562>
[04:34] <mup> Bug #1707563 opened: [2.2] no API document on /api/2.0/machines/{system_id}/ op=test <MAAS:New> <https://launchpad.net/bugs/1707563>
=== frankban|afk is now known as frankban
[11:07] <mup> Bug #1707625 opened: [2.3a1] MAAS crashes updating ntp conf <MAAS:New> <https://launchpad.net/bugs/1707625>
[11:13] <mup> Bug #1707625 changed: [2.3a1] MAAS crashes updating ntp conf <MAAS:New> <https://launchpad.net/bugs/1707625>
[11:16] <mup> Bug #1707625 opened: [2.3a1] MAAS crashes updating ntp conf <MAAS:New> <https://launchpad.net/bugs/1707625>
=== disposable3 is now known as disposable2
[16:11] <mup> Bug #1707674 opened: [2.3.0~alpha1, Subnet details] In subnet details, for managed allocation the interface wording is "Active" instead of "Enabled" <ui> <MAAS:New> <https://launchpad.net/bugs/1707674>
[16:17] <mup> Bug #1707675 opened: [2.3.0~alpha1, Subnet details] Description is right aligned on the screen instead of left aligned <ui> <MAAS:New> <https://launchpad.net/bugs/1707675>
=== frankban is now known as frankban|afk
[16:26] <mup> Bug #1707675 changed: [2.3.0~alpha1, Subnet details] Description is right aligned on the screen instead of left aligned <ui> <MAAS:New> <https://launchpad.net/bugs/1707675>
[16:41] <mup> Bug #1707675 opened: [2.3.0~alpha1, Subnet details] Description is right aligned on the screen instead of left aligned <ui> <MAAS:New> <https://launchpad.net/bugs/1707675>
[17:09] <plars> has anyone ever seen a situation where maas sets the interface back to unconfigured after starting an install?
[17:10] <plars> In our lab, we have a dhcp already that we need to use, so normally I set things to fabric1/DHCP and maas seems ok with that
[17:11] <plars> However there's another subnet for a different team that we can route to just fine, and it actually uses the same dhcp server. We have that as fabric0, and there is a subnet defined for it also. When I set up this system I configured the interface on it to fabric0/dhcp instead.
[17:11] <plars> when I tell it to deploy, I see it get the ip address, and our dhcp points it to the maas server for pxe so it starts the install. But something strange happens - if I watch the config screen for network interfaces, I see it revert to fabric1/unconfigured
[17:12] <plars> it finishes the install, sets it to local boot, and restarts the system, but of course when it comes back up it just has that unconfigured network interface
[17:13] <plars> I didn't see anything suspicious in the logs telling me why it was unconfiguring the network interface I configured already
[17:13] <plars> and clearly it was working well enough that it started the install