[03:17] <mup> Bug #1765661 changed: mode argument missing from snap <MAAS:Invalid> <https://launchpad.net/bugs/1765661>
[04:05] <mup> Bug #1766769 opened: [2.x, UI, enhacement] Add 'allow_proxy' to the UI per subnet basis <MAAS:Triaged> <https://launchpad.net/bugs/1766769>
[05:15] <mup> Bug #1766781 opened: [2.4, UI] Context menu regression <ui> <MAAS:Triaged by deadlight> <https://launchpad.net/bugs/1766781>
[12:14] <srihas> hi guys, we have an UCS environment. Inorder to control power from MaaS, we provide the API on the HTTPS but the problem is we have a selfsigned certificate and the MAAS is not making me add UCS power type. Is there a tweak that I can make?
[12:14] <srihas> thank you
[14:55] <mup> Bug #1765751 changed: django.db.utils.OperationalError: could not serialize access due to concurrent update during "migrate-conflicting-options" <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:Fix Released> <MAAS 2.3:Triaged> <https://launchpad.net/bugs/1765751>
[15:07] <mup> Bug #1703231 opened: Virsh Power address of VM changes by itself <maas> <MAAS:Incomplete> <https://launchpad.net/bugs/1703231>
[15:16] <mup> Bug #1703231 changed: Virsh Power address of VM changes by itself <maas> <MAAS:Incomplete> <https://launchpad.net/bugs/1703231>
[15:28] <mup> Bug #1703231 opened: Virsh Power address of VM changes by itself <maas> <MAAS:Incomplete> <https://launchpad.net/bugs/1703231>
=== setuid_ is now known as setuid