[04:25] <mup> Bug #1635107 changed: maas.power Error changing power state (on) while commissioning the node <MAAS:Expired> <https://launchpad.net/bugs/1635107>
[06:52] <mup> Bug #1635107 opened: maas.power Error changing power state (on) while commissioning the node <MAAS:Confirmed> <https://launchpad.net/bugs/1635107>
[12:37] <mwe1> hi there, does anybody knows website with a good tutotial how to trigger ansible via maas?
[13:02] <v92> mwe1: I'm planning to use ansible-pull method and do the ansible installation and configuration during deployment phase
[13:17] <mup> Bug #1722526 opened: [2.3] Cannot power manage a region/rack controller (which was a node deployed by MAAS) <MAAS:Triaged> <https://launchpad.net/bugs/1722526>
[13:32] <mup> Bug #1722531 opened: [2.3] No way to know what version of MAAS/curtin deployed  amachine <MAAS:New> <https://launchpad.net/bugs/1722531>
[13:32] <mup> Bug #1722532 opened: [2.3] No way to know what version of MAAS/curtin deployed  amachine <MAAS:Triaged by andreserl> <https://launchpad.net/bugs/1722532>
[13:36] <rbasak> mwe1: I don't know if this is relevant to you, but a common way to get newly started Ubuntu images to do things is to use cloud-init - including on MAAS, lxd, EC2, etc.
[13:38] <rbasak> It can add apt repositories, install packages, and then run commands on first boot, for example, it's present on all Ubuntu cloud images (and most other distributions' cloud images), and you can use MAAS to pass instructions to it.
[13:59] <roaksoax> /wi/win 4
[14:08] <mup> Bug #1722538 opened: Server header should provide MAAS version <papercut> <MAAS:Triaged> <https://launchpad.net/bugs/1722538>
[14:17] <mup> Bug #1722538 changed: Server header should provide MAAS version <papercut> <MAAS:Triaged> <https://launchpad.net/bugs/1722538>
[14:26] <mup> Bug #1722538 opened: Server header should provide MAAS version <papercut> <MAAS:Triaged> <https://launchpad.net/bugs/1722538>
[15:59] <mup> Bug #1722578 opened: Controller <> is running an older version of MAAS (less than 2.3.0) <cdo-qa> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1722578>
[16:35] <mup> Bug #1722589 opened: syslog full of "topology hint" logs <cdo-qa> <foundations-engine> <MAAS:In Progress by mpontillo> <https://launchpad.net/bugs/1722589>
[16:42] <jamesbenson> does anyone work with maas and juju?
[18:08] <mup> Bug #1722607 opened:  [2.3, HWTv2] Logs still sent with node object <MAAS:Triaged> <https://launchpad.net/bugs/1722607>
[18:08] <mup> Bug #1722609 opened:  [2.3, HWTv2] Add ability to view previous results on the node-results page <MAAS:Triaged> <https://launchpad.net/bugs/1722609>
[18:56] <mup> Bug #1722620 opened: [2.3] Failed to update regiond's process and endpoints; records may be out of date <MAAS:Triaged> <https://launchpad.net/bugs/1722620>
[19:14] <mup> Bug #1722620 changed: [2.3] Failed to update regiond's process and endpoints; records may be out of date <MAAS:Triaged> <https://launchpad.net/bugs/1722620>
[19:20] <mup> Bug #1722620 opened: [2.3] Failed to update regiond's process and endpoints; records may be out of date <MAAS:Triaged> <https://launchpad.net/bugs/1722620>
[20:17] <mup> Bug #1722646 opened: interfaces do not have ips <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:Incomplete> <https://launchpad.net/bugs/1722646>
[21:09] <mup> Bug #1719643 changed: [2.3, UI, HWTv2] Storage Card needs scrolling for multiple different disks <MAAS:Won't Fix by newell-jensen> <https://launchpad.net/bugs/1719643>
[21:30] <mup> Bug #1721743 opened: [2.3b2] Rack and region controller versions still not updated <MAAS:Triaged by mpontillo> <https://launchpad.net/bugs/1721743>
[22:00] <mup> Bug #1722665 opened: [2.3, HWTv2] MAAS stores a limited amount of test results <MAAS:Triaged> <https://launchpad.net/bugs/1722665>
[22:00] <mup> Bug #1722671 opened: [2.3, pod] Unable to delete a machine or a pod if the pod no longer exists <MAAS:New> <https://launchpad.net/bugs/1722671>