=== hazmat_ is now known as hazmat === icey_ is now known as icey [13:37] Bug #1573033 opened: [2.0 beta 3] api output is not consistent [13:38] Bug #1573035 opened: [2.0 beta 3] list-boot-images should report 'status' in lowercase === dooferlad_ is now known as dooferlad [14:02] Bug #1573046 opened: 14.04 images not available for commissioning as distrio-info --lts now reports xenial [14:32] Bug #1573072 opened: Cannot commission KVM node with 16.04 (xenial) [14:38] Bug #1573072 changed: Cannot commission KVM node with 16.04 (xenial) [14:47] Bug #1573072 opened: Support Xenial as commissioning image in 1.9 [17:03] Hi, I'm playing with MAAS (fresh 16.04 install, amd64) which shows Version 2.0.0 (beta3+bzr4941), yet is affected by https://bugs.launchpad.net/maas/+bug/1467584, which shows as fixed. When I tried to switch to the (stable) ppa, I noticed that it only has version 1.9. Any hints/suggestions? [17:08] For context, I need the CLI to change the DHCP pool range, because from the GUI I assigned it to a range that was too wide (your docs were a bit misleading in that they only mention the static/sticky IPs too late, way after the initial pool is set), and there is no way (that I could find) to change it from the GUI. [20:18] Bug #1573219 opened: Deleting user in UI leads to 500 [20:31] Is it possible to have WoL show up as a power type for a node? I.e. without proper IPMI or other BMC? [22:18] Bug #1573264 opened: enlistment fails: /tmp/sh.UZ7qJT/bin/maas-enlist: archdetect: not found [23:39] Bug #1573301 opened: list-boot-images fails when rack has no boot images [23:39] Bug #1573304 opened: maas-provision causing connection refused with TFTP back-end