[03:00] <mup> Bug #1846441 opened: [2.4.2] Custom layout is not applied with custom Image <sts> <MAAS:New> <https://launchpad.net/bugs/1846441>
[08:52] <mup> Bug #1846457 opened: [2.6] Composing a VM with an IP address on its interface is in Auto Assign state after commissioning <MAAS:New> <https://launchpad.net/bugs/1846457>
[12:10] <mup> Bug #1846441 changed: Custom layout is not applied with custom Image <sts> <MAAS:Invalid> <https://launchpad.net/bugs/1846441>
[12:13] <mup> Bug #1846441 opened: Custom layout is not applied with custom Image <sts> <MAAS:Invalid> <https://launchpad.net/bugs/1846441>
[12:19] <mup> Bug #1846441 changed: Custom layout is not applied with custom Image <sts> <MAAS:Invalid> <https://launchpad.net/bugs/1846441>
[12:40] <TimRiceSE> Hi! Has some change been released to maas/images recently? Suddenly today we're unable to deploy machines with a bond interface configured... cloud-init seems to fail with a "Not all expected physical devices present" runtime error... Exact same server was deployed two days ago with the exact same configuration :/