[07:08] <mup> Bug #1600121 opened: [2.0rc1] MAAS needs to use "sudo -n" everywhere "sudo" is used <MAAS:Triaged> <https://launchpad.net/bugs/1600121>
[08:20] <mup> Bug #1600135 opened: [2.0rc1] Calling the API with username/password authentication (via session cookie) results in undefined behavior <MAAS:Triaged> <https://launchpad.net/bugs/1600135>
[10:09] <junaidali> is maas 2.0 is compatible with 14.04?
[10:13] <junaidali> http://maas.ubuntu.com/docs2.0/install.html says to add repository ppa:maas/stable but maas 2.0 is still in beta
[11:50] <mup> Bug #1600198 opened: Bcache creation is unintuitive and causes traceback <MAAS:New> <https://launchpad.net/bugs/1600198>
[13:48] <mup> Bug #1562249 changed: Failed to deploy machine with HP Smart Array Raid 6i <curtin-clear-holders> <curtin-sru> <landscape> <curtin:In Progress> <Landscape Server:Invalid> <MAAS:Invalid> <https://launchpad.net/bugs/1562249>
[13:48] <mup> Bug #1598358 changed: [juju beta10] With MAAS, node allocated but never told to deploy. <oil> <juju-core:New> <MAAS:Invalid> <https://launchpad.net/bugs/1598358>
[13:57] <mup> Bug #1409949 changed: Backdoored images are overwritten by MAAS <oil> <MAAS:Won't Fix> <https://launchpad.net/bugs/1409949>
[14:06] <mup> Bug #1409949 opened: Backdoored images are overwritten by MAAS <oil> <MAAS:Won't Fix> <https://launchpad.net/bugs/1409949>
[14:18] <mup> Bug #1409949 changed: Backdoored images are overwritten by MAAS <oil> <MAAS:Won't Fix> <https://launchpad.net/bugs/1409949>
[14:22] <webmichael> anyone know how to change the commissioning url for a node from archive.ubuntu.com to something else ? looking around could find a good answer yet
[14:22] <webmichael> could not
[14:27] <mup> Bug #1597969 changed: Change boot device and not recommissioning causes curtain failure <MAAS:Invalid> <https://launchpad.net/bugs/1597969>
[14:27] <mup> Bug #1600249 opened: Static IP assignement reverts last octed to "1" <MAAS:New> <https://launchpad.net/bugs/1600249>
[14:41] <gimmic> Anyone using maas to install CentOS?
[14:48] <five0va> hello all! I've been running into an issue attempting to add another VLAN or Subnet to MAAS (MAAS Version 2.0.0 (beta3+bzr4941)). I'm running this on Ubuntu 16.04 - http://askubuntu.com/questions/790732/maas-2-0-0-extra-data-when-adding-subnet
[14:57] <mup> Bug #1600259 opened: [2.0] reverse DNS sometimes assigns FQDN where it should assign IFACE.FQDN <MAAS:New for lamont> <MAAS 2.0:New for lamont> <MAAS trunk:New for lamont> <https://launchpad.net/bugs/1600259>
[14:57] <mup> Bug #1600264 opened: [2.0rc1] Unable to connect to BMC causes a traceback <MAAS:New> <MAAS 2.0:New> <MAAS trunk:New> <https://launchpad.net/bugs/1600264>
[15:08] <gimmic> I don't see maas-image-builder
[15:12] <gimmic> nevermind, failure to comprehend the manual
[15:14] <gimmic> even with the repos, can't find maas-image-builder
[15:21] <mup> Bug #1600267 opened: Can't add aliases to DHCP interfaces <MAAS:New> <https://launchpad.net/bugs/1600267>
[15:24] <kiko> gimmic, what are you trying to do?
[15:32] <gimmic> I'm trying to find the maas-image-builder per documentation
[15:32] <gimmic> I'm going to need to deploy CentOS
[15:49] <roaksoax> gimmic: maas-image-builder has been deprecated now as CentOS is provided as part of the images you can download
[15:49] <roaksoax> gimmic: you need to use the 'daily' image streams though  to be able to find the CentOS images
[15:54] <dannf> roaksoax: would you rather i wait till the doc changes are merged into trunk, so that the backported revs are recorded, or just do a separate branch w/ cherrypicks from my branch?
[16:02] <gQuigs> maas 1.9.3 should be able to commision nodes with 16.04 even if your maas node is 14.04, right?
[16:03] <gQuigs> comissioning with 14.04 and then installing 16.04 works
[16:15] <mup> Bug #1600285 opened: please drop arm64/efi grub module workaround <MAAS:New> <https://launchpad.net/bugs/1600285>
[16:17] <gimmic> roaksoax: thanks, how do I enable 'daily' image streams?
[16:21] <mup> Bug #1600285 changed: please drop arm64/efi grub module workaround <MAAS:New> <https://launchpad.net/bugs/1600285>
[16:22] <five0va> Finally was able to a subnet working - exact steps need to be taken or non-descript errors are thrown (like the data error I was encountering!). Now I'm encountering an issue where this MAAS deployment wasn't setup with DHCP.. how do I change this?
[16:24] <mup> Bug #1600285 opened: please drop arm64/efi grub module workaround <MAAS:New> <https://launchpad.net/bugs/1600285>
[17:10] <webmichael> you want maas to manage dhcp for that subnet ?
[17:11] <roaksoax> gimmic: go to the settings page and the image source.
[17:15] <gimmic> I don't see an image source
[17:15] <gimmic> I see the ubuntu main archive
[17:15] <webmichael> look for boot images
[17:16] <gimmic> got it.
[18:05] <gQuigs> found a bug for it: https://bugs.launchpad.net/maas/+bug/1573072
[18:06] <gQuigs> that seems like more importance than wishlist though... thoughts?
[18:42] <mup> Bug #1600328 opened: [2.0rc1] Traceback when adding a machine via the API, but it is added nonetheless <MAAS:New> <https://launchpad.net/bugs/1600328>