[06:01] <mup> Bug #1946914 opened: vmcluster.get websocket api doesn't appear to work <blocking-ui> <websocket-api> <MAAS:New> <https://launchpad.net/bugs/1946914>
[06:04] <mup> Bug #1946914 changed: vmcluster.get websocket api doesn't appear to work <blocking-ui> <websocket-api> <MAAS:New> <https://launchpad.net/bugs/1946914>
[06:07] <mup> Bug #1946914 opened: vmcluster.get websocket api doesn't appear to work <blocking-ui> <websocket-api> <MAAS:New> <https://launchpad.net/bugs/1946914>
[17:02] <mup> Bug #1947013 opened: When using RAID 0 in MAAS3.0, the calculated total disk size is incorrect is <MAAS:New> <https://launchpad.net/bugs/1947013>
[17:53] <mup> Bug #1947019 opened: MAAS 3.0 ignores  Allow SSH access and prevent machine powering off <blocks-hwcert-server> <MAAS:New> <https://launchpad.net/bugs/1947019>
[17:56] <mup> Bug #1947019 changed: MAAS 3.0 ignores  Allow SSH access and prevent machine powering off <blocks-hwcert-server> <MAAS:New> <https://launchpad.net/bugs/1947019>
[17:59] <mup> Bug #1947019 opened: MAAS 3.0 ignores  Allow SSH access and prevent machine powering off <blocks-hwcert-server> <MAAS:New> <https://launchpad.net/bugs/1947019>
[21:38] <mup> Bug #1947052 opened: systemd-resolved failure when commissioning machine with 12 NICs <blocks-hwcert-server> <MAAS:New> <https://launchpad.net/bugs/1947052>