[04:30] Bug #1834551 changed: Node installation failure - 'curtin' curtin command install [04:33] Bug #1834551 opened: Node installation failure - 'curtin' curtin command install [04:36] Bug #1834551 changed: Node installation failure - 'curtin' curtin command install === exsdev0 is now known as exsdev === exsdev0 is now known as exsdev [07:22] Bug #1805907 changed: Feature Request: MAAS node discovery default hostname + random_name creation [08:01] Bug #1796395 changed: feature: support multiple regiond endpoints [08:07] Bug #1796395 opened: feature: support multiple regiond endpoints [08:13] Bug #1796395 changed: feature: support multiple regiond endpoints [13:01] Bug #1817663 changed: maas-dhcpd not running due to missing dhcpd.conf after restarting maas-regiond [13:07] Bug #1817663 opened: maas-dhcpd not running due to missing dhcpd.conf after restarting maas-regiond [13:13] Bug #1817663 changed: maas-dhcpd not running due to missing dhcpd.conf after restarting maas-regiond [13:46] Bug #1812275 opened: power-on for an acquired node deploys the machine [13:52] Bug #1812275 changed: power-on for an acquired node deploys the machine [14:04] Bug #1791957 changed: [feature] support setting target_session_attrs postgres option by passing additional options to a django database backend [14:04] Bug #1828079 changed: [ESXi] Disk info for datastores delayed with no callback [14:07] Bug #1791957 opened: [feature] support setting target_session_attrs postgres option by passing additional options to a django database backend [14:07] Bug #1812275 opened: power-on for an acquired node deploys the machine [14:07] Bug #1828079 opened: [ESXi] Disk info for datastores delayed with no callback [14:10] Bug #1791957 changed: [feature] support setting target_session_attrs postgres option by passing additional options to a django database backend [14:10] Bug #1812275 changed: power-on for an acquired node deploys the machine [14:10] Bug #1828079 changed: [ESXi] Disk info for datastores delayed with no callback [14:13] Bug #1791957 opened: [feature] support setting target_session_attrs postgres option by passing additional options to a django database backend [14:13] Bug #1812275 opened: power-on for an acquired node deploys the machine [14:13] Bug #1828079 opened: [ESXi] Disk info for datastores delayed with no callback [14:16] Bug #1791957 changed: [feature] support setting target_session_attrs postgres option by passing additional options to a django database backend [14:16] Bug #1812275 changed: power-on for an acquired node deploys the machine [14:16] Bug #1828079 changed: [ESXi] Disk info for datastores delayed with no callback [15:01] Bug #1812275 opened: Document that power-on for an acquired node deploys the machine [15:10] Bug #1812275 changed: Document that power-on for an acquired node deploys the machine [15:13] Bug #1812275 opened: Document that power-on for an acquired node deploys the machine [15:17] Bug #1845220 opened: Add WS API for SSL keys [15:26] Bug #1845220 changed: Add WS API for SSL keys [15:29] Bug #1845220 opened: Add WS API for SSL keys [17:08] Bug #1844162 changed: Instructions missing in MaaS manual for disabling the reverse proxy running on port 8000/3128 [17:14] Bug #1844162 opened: Instructions missing in MaaS manual for disabling the reverse proxy running on port 8000/3128 [17:17] Bug #1844162 changed: Instructions missing in MaaS manual for disabling the reverse proxy running on port 8000/3128 [18:05] 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] maybe im not setting the parent interface (that doesnt need an ip) incorrectly? [18:14] guess this irc is pretty inactive eh? [18:48] We're running an older version of maas, (2.3) and I'm seeing veeery slow maas cli queries [18:49] 145 bare metal machines, and doing a simple 'maas $account machine read' is taking 4 minutes [18:49] Even reading 7 tags takes 2.4 seconds.. seems like something is borked, but I don't see errors anywhere [22:05] 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] seems like an issue with maas itself.