[02:11] <mup> Bug #1727900 opened: After applying "Power off" action in nodes listing, the power doesn't update unless it is manually queried <MAAS:Confirmed> <https://launchpad.net/bugs/1727900>
[03:11] <mup> Bug #1704026 changed: [2.3] Strange error when registering external rack controller <ha> <MAAS:Invalid> <https://launchpad.net/bugs/1704026>
[03:14] <mup> Bug #1704026 opened: [2.3] Strange error when registering external rack controller <ha> <MAAS:Invalid> <https://launchpad.net/bugs/1704026>
[03:17] <mup> Bug #1682206 changed: [2.2 rc1] commissioning does not timeout for systems that fail to PXE <oil> <MAAS:Invalid> <https://launchpad.net/bugs/1682206>
[03:17] <mup> Bug #1704026 changed: [2.3] Strange error when registering external rack controller <ha> <MAAS:Invalid> <https://launchpad.net/bugs/1704026>
[03:20] <mup> Bug #1682206 opened: [2.2 rc1] commissioning does not timeout for systems that fail to PXE <oil> <MAAS:Invalid> <https://launchpad.net/bugs/1682206>
[03:41] <mup> Bug #1682206 changed: [2.2 rc1] commissioning does not timeout for systems that fail to PXE <oil> <MAAS:Invalid> <https://launchpad.net/bugs/1682206>
[05:49] <TomL> Hi, I'm using MaaS ver. 2.2.2 to deploy a Centos client but haven't been successful.  The root.tgz have been pulled down successfully and cloud-init seems to run fine.
[05:50] <TomL> Upon reboot, I get this error "Loading centos/amd64/ga-16.04/centos70/no-such-image/boot-kernel... failed: No such file or directory"
[05:51] <TomL> I booted into rescue mode and checked the cloud-init logs and didn't find anything.  I also checked both the regiond and rackd logs.
[05:51] <TomL> Can someone direct me to where I can look?
[07:53] <mup> Bug #1727962 opened: Intermittent failure: TestDeviceHandler.test_list_num_queries_is_the_expected_number <MAAS:New> <https://launchpad.net/bugs/1727962>
[10:12] <mup> Bug #1728004 opened: Intermittent failure: TestMaasRunRemoteScripts.test_heartbeat <MAAS:New> <https://launchpad.net/bugs/1728004>
[11:41] <Miouge> roaksoax: is it possible/useful to use MAAS as DHCP on the IPMI network? (in addition to the normal PXE DHCP that is)
[14:22] <roaksoax> Miouge: yes/no, I would never rely on dhcp for ipmi itself
[14:23] <roaksoax> Miouge: what you could do instead is add devices in MAAS with static IP assignment for your bmc's
[14:23] <Miouge> It’s a pain to set IPMI IPs manually, I am wondering if MAAS can help there either with DHCP of ipmitool to configure the static IP
[14:24] <Miouge> (since I already use MAAS for the PXE boot)
[15:00] <roaksoax> Miouge: you can add "devices" in MAAS with static ip assingments for the bmc mac addresss
[15:01] <roaksoax> Miouge: the bmc will dhcp from maas
[15:01] <Miouge> OK, I’ll give this a shot
[15:02] <Miouge> The idea is to use DHCP to distribute the IP config, but have it static with MAC based reservations
[15:03] <roaksoax> Miouge: yes, you create a static map in maas by adding a device with static IP assignment, and maas will servcer it via dhcp
[15:07] <Miouge> roaksoax: OK, on another topic I can read the interfaces and ip_addresses from the Machine objects, but I don’t see any “disks” attribute or similar. How do I check the storage layout via libmaas?
[15:13] <roaksoax> Miouge: let me check if that landed. I remember we had a few branches that needed tests before landing
[15:14] <roaksoax> Miouge: if not, they will be landing next week
[20:27] <mup> Bug #1727561 changed: [2.3, HA] Machines fails commissioning and testing and MAAS shows no errors <MAAS:Invalid> <https://launchpad.net/bugs/1727561>
[20:33] <mup> Bug #1727561 opened: [2.3, HA] Machines fails commissioning and testing and MAAS shows no errors <MAAS:Invalid> <https://launchpad.net/bugs/1727561>
[20:45] <mup> Bug #1727561 changed: [2.3, HA] Machines fails commissioning and testing and MAAS shows no errors <MAAS:Invalid> <https://launchpad.net/bugs/1727561>
[21:27] <mup> Bug #1728154 opened: [2.3, HWTv2] Hardware test names dropped from list <MAAS:New> <https://launchpad.net/bugs/1728154>