[13:12] <mup> Bug #1506856 opened: Show devices with a parent on the node details page <ui> <ux> <MAAS:Triaged by carlaberkers> <https://launchpad.net/bugs/1506856>
[14:12] <mup> Bug #1428831 changed: USB drive tagged "rotary" <ui> <MAAS:Invalid> <https://launchpad.net/bugs/1428831>
[15:51] <mup> Bug #1506909 opened: Can't change node name due to unrelated error <MAAS:New> <https://launchpad.net/bugs/1506909>
[16:54] <mup> Bug #1497392 opened: maas text-mode "node-group-interface" bug fails with MAAS 1.8.2+bzr4041-0ubuntu1~trusty1 <MAAS:Confirmed> <https://launchpad.net/bugs/1497392>
[17:13] <mgz> roaksoax: wotcha, trying to get juju working with maas 1.9 and centos - the auto image import however is using 'centos70' rather than 'centos7' as the release name,
[17:14] <mgz> and then manually importing a custom image with the right name doesn't seem to get used when selecting release
[17:15] <mgz> have you tried doing this at all?
[17:48] <mup> Bug #1497392 changed: maas text-mode "node-group-interface" bug fails with MAAS 1.8.2+bzr4041-0ubuntu1~trusty1 <MAAS:Invalid> <https://launchpad.net/bugs/1497392>
[17:51] <mup> Bug #1497392 opened: maas text-mode "node-group-interface" bug fails with MAAS 1.8.2+bzr4041-0ubuntu1~trusty1 <MAAS:Invalid> <https://launchpad.net/bugs/1497392>
[17:54] <mup> Bug #1497392 changed: maas text-mode "node-group-interface" bug fails with MAAS 1.8.2+bzr4041-0ubuntu1~trusty1 <MAAS:Invalid> <https://launchpad.net/bugs/1497392>
[18:48] <pmatulis> i have a kvm guest with two network adapters. do i need to do anything special for it to be enlisted?
[18:57] <roaksoax> win 13
[18:57] <roaksoax> mgz: how are you importing a custom image? as custom or as centos?
[18:59] <roaksoax> mgz: if it is as "centos" then, it is not really a custom image, but rather, the above image will take presedence and the imported manually ignored
[18:59] <roaksoax> mgz: please, do file a bug that highlights the change, so we can provide an alias that centos7 -> centos70
[19:19] <mup> Bug #1506991 opened: maas should tell cloud-init not to try metadata service on every boot <falkor:New> <MAAS:New> <https://launchpad.net/bugs/1506991>
[19:22] <roaksoax> pmatulis: no not really? MAAS will discover both NIC's and add them in MAAS
[19:22] <mup> Bug #1506991 changed: maas should tell cloud-init not to try metadata service on every boot <falkor:New> <MAAS:New> <https://launchpad.net/bugs/1506991>
[19:28] <mup> Bug #1506991 opened: maas should tell cloud-init not to try metadata service on every boot <falkor:New> <MAAS:New> <https://launchpad.net/bugs/1506991>
[19:41] <pmatulis> roaksoax: ok