[00:09] <mup> Bug #1710308 opened: [2.2] MAAS should throttle bind reloads <MAAS:Triaged> <MAAS 2.2:Triaged> <https://launchpad.net/bugs/1710308>
[00:09] <mup> Bug #1710310 opened: [2.2] DNS service monitoring should issue test queries <MAAS:Triaged> <https://launchpad.net/bugs/1710310>
[04:18] <mup> Bug #1588466 changed: gpg --batch --verify during maas install causes Unhandled Error <cdo-qa> <MAAS:Expired> <simplestreams:Incomplete> <https://launchpad.net/bugs/1588466>
[04:36] <mup> Bug #1588466 opened: gpg --batch --verify during maas install causes Unhandled Error <cdo-qa> <MAAS:Expired> <simplestreams:Incomplete> <https://launchpad.net/bugs/1588466>
[04:42] <mup> Bug #1588466 changed: gpg --batch --verify during maas install causes Unhandled Error <cdo-qa> <MAAS:Expired> <simplestreams:Incomplete> <https://launchpad.net/bugs/1588466>
[06:21] <maasCluster> I've just recently setup MAAS Region controller and cannot get additional MAAS nodes to remain on during boot up... Get a power error each time, and the nodes then turnoff after getting commands from MAAS controller
[06:21] <maasCluster> Can anyone help please
[06:22] <maasCluster> I occasion can get one or two of the nodes to stay on (green on, and ready state)... but then when trying to get the 3rd node on, everything powers off
[12:14] <jcordeiro> is there a known bug that makes my MAAS machine go 100% cpu on idle?
[12:15] <jcordeiro> jesus lutostag ... thats some bad connection you have
[12:19] <jcordeiro> with 8 cpus my load is 14
[12:20] <jcordeiro> the thing using all my cpu is:
[12:20] <jcordeiro>  9332 maas      20   0 1522636 190196  19832 R  42.4  1.2 666:15.00 twistd3
[12:21] <jcordeiro> https://bugs.launchpad.net/maas/+bug/1558314 ...
[12:22] <jcordeiro> https://bugs.launchpad.net/maas/+bug/1705518
[12:24] <jcordeiro> lol, that was fast on lutostag