[05:19] Bug #1876855 opened: "Power types" websocket api doesn't match "add chassis" api [05:22] Bug #1876855 changed: "Power types" websocket api doesn't match "add chassis" api [05:28] Bug #1876855 opened: "Power types" websocket api doesn't match "add chassis" api [06:56] Bug #1876860 opened: Allow some notifications to be non-dismissable [06:59] Bug #1876860 changed: Allow some notifications to be non-dismissable [07:02] Bug #1876860 opened: Allow some notifications to be non-dismissable [07:08] Bug #1849213 changed: MAAS creates user but fails to set priv level [07:14] Bug #1849213 opened: MAAS creates user but fails to set priv level [07:20] Bug #1849213 changed: MAAS creates user but fails to set priv level [07:23] Bug #1849213 opened: MAAS creates user but fails to set priv level [07:26] Bug #1849213 changed: MAAS creates user but fails to set priv level [07:29] Bug #1849213 opened: MAAS creates user but fails to set priv level [07:32] Bug #1849213 changed: MAAS creates user but fails to set priv level [08:08] Bug #1737428 changed: VRF support to solve routing problems associated with multi-homing [13:11] Bug #1876921 opened: Passwords are not hidden when adding a LXC KVM [16:42] i have a machine which is failing commissioning with this error: Marking node failed - Missing boot image (xxx) - tried multiple distros, none work - other machines commission and deploy fine [16:42] no related rsyslogs [17:17] I have another issue with a ppc64el machine, which 2 connected interfaces. I want one to have an autoassigned IP and the other not. I select that the PXE interface should be the one which is autoassigned (i dont know if this is relevant) and when the machine is eventually deployed it doesnt have a default route. i will log a bug w more info but curious if anyone knows that the PXE switching thing is [17:17] related to no default route