| mup | Bug #1876855 opened: "Power types" websocket api doesn't match "add chassis" api <websocket-api> <MAAS:New> <https://launchpad.net/bugs/1876855> | 05:19 |
|---|---|---|
| mup | Bug #1876855 changed: "Power types" websocket api doesn't match "add chassis" api <websocket-api> <MAAS:New> <https://launchpad.net/bugs/1876855> | 05:22 |
| mup | Bug #1876855 opened: "Power types" websocket api doesn't match "add chassis" api <websocket-api> <MAAS:New> <https://launchpad.net/bugs/1876855> | 05:28 |
| mup | Bug #1876860 opened: Allow some notifications to be non-dismissable <websocket-api> <MAAS:Triaged> <https://launchpad.net/bugs/1876860> | 06:56 |
| mup | Bug #1876860 changed: Allow some notifications to be non-dismissable <websocket-api> <MAAS:Triaged> <https://launchpad.net/bugs/1876860> | 06:59 |
| mup | Bug #1876860 opened: Allow some notifications to be non-dismissable <websocket-api> <MAAS:Triaged> <https://launchpad.net/bugs/1876860> | 07:02 |
| mup | Bug #1849213 changed: MAAS creates user but fails to set priv level <blocks-hwcert-server> <MAAS:Expired> <https://launchpad.net/bugs/1849213> | 07:08 |
| mup | Bug #1849213 opened: MAAS creates user but fails to set priv level <blocks-hwcert-server> <MAAS:Expired> <https://launchpad.net/bugs/1849213> | 07:14 |
| mup | Bug #1849213 changed: MAAS creates user but fails to set priv level <blocks-hwcert-server> <MAAS:Expired> <https://launchpad.net/bugs/1849213> | 07:20 |
| mup | Bug #1849213 opened: MAAS creates user but fails to set priv level <blocks-hwcert-server> <MAAS:Expired> <https://launchpad.net/bugs/1849213> | 07:23 |
| mup | Bug #1849213 changed: MAAS creates user but fails to set priv level <blocks-hwcert-server> <MAAS:Expired> <https://launchpad.net/bugs/1849213> | 07:26 |
| mup | Bug #1849213 opened: MAAS creates user but fails to set priv level <blocks-hwcert-server> <MAAS:Expired> <https://launchpad.net/bugs/1849213> | 07:29 |
| mup | Bug #1849213 changed: MAAS creates user but fails to set priv level <blocks-hwcert-server> <MAAS:Expired> <https://launchpad.net/bugs/1849213> | 07:32 |
| mup | Bug #1737428 changed: VRF support to solve routing problems associated with multi-homing <cpe-onsite> <kernel-da-key> <sts> <juju:Incomplete> <MAAS:Invalid> <linux (Ubuntu):Incomplete> <https://launchpad.net/bugs/1737428> | 08:08 |
| mup | Bug #1876921 opened: Passwords are not hidden when adding a LXC KVM <ui> <MAAS:Confirmed> <https://launchpad.net/bugs/1876921> | 13:11 |
| admcleod | 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 |
| admcleod | no related rsyslogs | 16:42 |
| admcleod | 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 |
| admcleod | related to no default route | 17:17 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!