[04:30] <mup> Bug #1834551 changed: Node installation failure - 'curtin' curtin command install <curtin:Expired> <MAAS:Expired> <https://launchpad.net/bugs/1834551>
[04:33] <mup> Bug #1834551 opened: Node installation failure - 'curtin' curtin command install <curtin:Expired> <MAAS:Expired> <https://launchpad.net/bugs/1834551>
[04:36] <mup> Bug #1834551 changed: Node installation failure - 'curtin' curtin command install <curtin:Expired> <MAAS:Expired> <https://launchpad.net/bugs/1834551>
[07:22] <mup> Bug #1805907 changed: Feature Request: MAAS node discovery default hostname + random_name creation <MAAS:Invalid> <https://launchpad.net/bugs/1805907>
[08:01] <mup> Bug #1796395 changed: feature: support multiple regiond endpoints <cpe-onsite> <OpenStack hacluster charm:Invalid> <MAAS:Invalid> <https://launchpad.net/bugs/1796395>
[08:07] <mup> Bug #1796395 opened: feature: support multiple regiond endpoints <cpe-onsite> <OpenStack hacluster charm:Invalid> <MAAS:Invalid> <https://launchpad.net/bugs/1796395>
[08:13] <mup> Bug #1796395 changed: feature: support multiple regiond endpoints <cpe-onsite> <OpenStack hacluster charm:Invalid> <MAAS:Invalid> <https://launchpad.net/bugs/1796395>
[13:01] <mup> Bug #1817663 changed: maas-dhcpd not running due to missing dhcpd.conf after restarting maas-regiond <MAAS:Triaged by blake-rouse> <MAAS 2.6:Won't Fix> <https://launchpad.net/bugs/1817663>
[13:07] <mup> Bug #1817663 opened: maas-dhcpd not running due to missing dhcpd.conf after restarting maas-regiond <MAAS:Triaged by blake-rouse> <MAAS 2.6:Won't Fix> <https://launchpad.net/bugs/1817663>
[13:13] <mup> Bug #1817663 changed: maas-dhcpd not running due to missing dhcpd.conf after restarting maas-regiond <MAAS:Triaged by blake-rouse> <MAAS 2.6:Won't Fix> <https://launchpad.net/bugs/1817663>
[13:46] <mup> Bug #1812275 opened: power-on for an acquired node deploys the machine <sts> <MAAS:New> <https://launchpad.net/bugs/1812275>
[13:52] <mup> Bug #1812275 changed: power-on for an acquired node deploys the machine <sts> <MAAS:New> <https://launchpad.net/bugs/1812275>
[14:04] <mup> Bug #1791957 changed: [feature] support setting target_session_attrs postgres option by passing additional options to a django database backend <cpe-onsite> <feature> <MAAS:Invalid> <https://launchpad.net/bugs/1791957>
[14:04] <mup> Bug #1828079 changed: [ESXi] Disk info for datastores delayed with no callback <esxi> <MAAS:Invalid> <https://launchpad.net/bugs/1828079>
[14:07] <mup> Bug #1791957 opened: [feature] support setting target_session_attrs postgres option by passing additional options to a django database backend <cpe-onsite> <feature> <MAAS:Invalid> <https://launchpad.net/bugs/1791957>
[14:07] <mup> Bug #1812275 opened: power-on for an acquired node deploys the machine <sts> <MAAS:Invalid> <https://launchpad.net/bugs/1812275>
[14:07] <mup> Bug #1828079 opened: [ESXi] Disk info for datastores delayed with no callback <esxi> <MAAS:Invalid> <https://launchpad.net/bugs/1828079>
[14:10] <mup> Bug #1791957 changed: [feature] support setting target_session_attrs postgres option by passing additional options to a django database backend <cpe-onsite> <feature> <MAAS:Invalid> <https://launchpad.net/bugs/1791957>
[14:10] <mup> Bug #1812275 changed: power-on for an acquired node deploys the machine <sts> <MAAS:Invalid> <https://launchpad.net/bugs/1812275>
[14:10] <mup> Bug #1828079 changed: [ESXi] Disk info for datastores delayed with no callback <esxi> <MAAS:Invalid> <https://launchpad.net/bugs/1828079>
[14:13] <mup> Bug #1791957 opened: [feature] support setting target_session_attrs postgres option by passing additional options to a django database backend <cpe-onsite> <feature> <MAAS:Invalid> <https://launchpad.net/bugs/1791957>
[14:13] <mup> Bug #1812275 opened: power-on for an acquired node deploys the machine <sts> <MAAS:Invalid> <https://launchpad.net/bugs/1812275>
[14:13] <mup> Bug #1828079 opened: [ESXi] Disk info for datastores delayed with no callback <esxi> <MAAS:Invalid> <https://launchpad.net/bugs/1828079>
[14:16] <mup> Bug #1791957 changed: [feature] support setting target_session_attrs postgres option by passing additional options to a django database backend <cpe-onsite> <feature> <MAAS:Invalid> <https://launchpad.net/bugs/1791957>
[14:16] <mup> Bug #1812275 changed: power-on for an acquired node deploys the machine <sts> <MAAS:Invalid> <https://launchpad.net/bugs/1812275>
[14:16] <mup> Bug #1828079 changed: [ESXi] Disk info for datastores delayed with no callback <esxi> <MAAS:Invalid> <https://launchpad.net/bugs/1828079>
[15:01] <mup> Bug #1812275 opened: Document that power-on for an acquired node deploys the machine <doc> <sts> <MAAS:Triaged> <https://launchpad.net/bugs/1812275>
[15:10] <mup> Bug #1812275 changed: Document that power-on for an acquired node deploys the machine <doc> <sts> <MAAS:Triaged> <https://launchpad.net/bugs/1812275>
[15:13] <mup> Bug #1812275 opened: Document that power-on for an acquired node deploys the machine <doc> <sts> <MAAS:Triaged> <https://launchpad.net/bugs/1812275>
[15:17] <mup> Bug #1845220 opened: Add WS API for SSL keys <websocket-api> <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1845220>
[15:26] <mup> Bug #1845220 changed: Add WS API for SSL keys <websocket-api> <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1845220>
[15:29] <mup> Bug #1845220 opened: Add WS API for SSL keys <websocket-api> <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1845220>
[17:08] <mup> Bug #1844162 changed: Instructions missing in MaaS manual for disabling the reverse proxy running on port 8000/3128  <field-critical> <MAAS:Fix Released by adam-collard> <https://launchpad.net/bugs/1844162>
[17:14] <mup> Bug #1844162 opened: Instructions missing in MaaS manual for disabling the reverse proxy running on port 8000/3128  <field-critical> <MAAS:Fix Released by adam-collard> <https://launchpad.net/bugs/1844162>
[17:17] <mup> Bug #1844162 changed: Instructions missing in MaaS manual for disabling the reverse proxy running on port 8000/3128  <field-critical> <MAAS:Fix Released by adam-collard> <https://launchpad.net/bugs/1844162>
[18:05] <killcity> has anyone here had success with a vlan sub interface on a bond? im getting some hanging despite the bond being created correctly and the sub interface being there with an ip.
[18:05] <killcity> maybe im not setting the parent interface (that doesnt need an ip) incorrectly?
[18:14] <killcity> guess this irc is pretty inactive eh?
[18:48] <gimmic> We're running an older version of maas, (2.3) and I'm seeing veeery slow maas cli queries
[18:49] <gimmic> 145 bare metal machines, and doing a simple 'maas $account machine read' is taking 4 minutes
[18:49] <gimmic> Even reading 7 tags takes 2.4 seconds.. seems like something is borked, but I don't see errors anywhere
[22:05] <killcity> anyone have any idea why i cant ping the controller from another vlan, when i can clearly see the packets getting there? iptables also seems disabled. all vlans are in the same space.
[22:05] <killcity> seems like an issue with maas itself.