[09:16] <mup> Bug #1353495 changed: [API] MAAS doesn't have a consistent error response format <api> <tech-debt> <track> <MAAS:Invalid> <https://launchpad.net/bugs/1353495>
[09:22] <mup> Bug #1353495 opened: [API] MAAS doesn't have a consistent error response format <api> <tech-debt> <track> <MAAS:Invalid> <https://launchpad.net/bugs/1353495>
[09:25] <mup> Bug #1353495 changed: [API] MAAS doesn't have a consistent error response format <api> <tech-debt> <track> <MAAS:Invalid> <https://launchpad.net/bugs/1353495>
[09:25] <mup> Bug #1382172 changed: drivers.yaml should be in /var/lib/maas/ <tech-debt> <MAAS:Invalid> <https://launchpad.net/bugs/1382172>
[09:34] <mup> Bug #1382172 opened: drivers.yaml should be in /var/lib/maas/ <tech-debt> <MAAS:Invalid> <https://launchpad.net/bugs/1382172>
[09:40] <mup> Bug #1382172 changed: drivers.yaml should be in /var/lib/maas/ <tech-debt> <MAAS:Invalid> <https://launchpad.net/bugs/1382172>
[09:43] <mup> Bug #1382172 opened: drivers.yaml should be in /var/lib/maas/ <tech-debt> <MAAS:Invalid> <https://launchpad.net/bugs/1382172>
[09:46] <mup> Bug #1382172 changed: drivers.yaml should be in /var/lib/maas/ <tech-debt> <MAAS:Invalid> <https://launchpad.net/bugs/1382172>
[09:55] <mup> Bug #1633727 changed: [2.1] connectionpool leaks python-isms in log <log> <MAAS:Invalid> <https://launchpad.net/bugs/1633727>
[09:55] <mup> Bug #1685490 changed: DHCP snippet validation should prompt user to add a global snippet for missing option and link to relevant documents. <ui> <ux> <MAAS:Won't Fix> <maas-ui:New> <https://launchpad.net/bugs/1685490>
[09:55] <mup> Bug #1685629 changed: MAAS should validate any proxy <MAAS:Fix Released> <https://launchpad.net/bugs/1685629>
[10:28] <mup> Bug #1702649 changed: MAAS should assess PostGRES configuration <performance> <MAAS:Invalid> <https://launchpad.net/bugs/1702649>
[11:19] <BedMan> does anyone ever chat in here?
[11:20] <BedMan> I was wondering how to change the assoicated fabric with an interface on a system that's in a state other than "ready" (or 4) 
[11:20] <BedMan> it must be able to be done, since the fabric is set after the system was deployed anyway to a spurious value
[16:23] <mup> Bug #2008273 opened: networks on controllers not detected when proxy is present <cdo-qa> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/2008273>
[16:26] <mup> Bug #2008273 changed: networks on controllers not detected when proxy is present <cdo-qa> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/2008273>
[16:29] <mup> Bug #2008273 opened: networks on controllers not detected when proxy is present <cdo-qa> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/2008273>
[16:29] <mup> Bug #2008275 opened: Intel AMT support is broken in MAAS 3.3.0 <MAAS:New> <https://launchpad.net/bugs/2008275>
[16:35] <mup> Bug #2008275 changed: Intel AMT support is broken in MAAS 3.3.0 <MAAS:New> <https://launchpad.net/bugs/2008275>
[16:38] <mup> Bug #2008275 opened: Intel AMT support is broken in MAAS 3.3.0 <MAAS:New> <https://launchpad.net/bugs/2008275>
[16:50] <mup> Bug #2008275 changed: Intel AMT support is broken in MAAS 3.3.0 <MAAS:New> <https://launchpad.net/bugs/2008275>
[16:53] <mup> Bug #2008275 opened: Intel AMT support is broken in MAAS 3.3.0 <MAAS:New> <https://launchpad.net/bugs/2008275>
[21:35] <mup> Bug #2008421 opened: MAAS sometimes fails to commission itself on installation <MAAS:New> <https://launchpad.net/bugs/2008421>
[21:38] <mup> Bug #2008421 changed: MAAS sometimes fails to commission itself on installation <MAAS:New> <https://launchpad.net/bugs/2008421>
[21:47] <mup> Bug #2008421 opened: MAAS sometimes fails to commission itself on installation <MAAS:New> <https://launchpad.net/bugs/2008421>