[04:47] <mup> Bug #1707253 changed: pxe boot fails with http enabled <cdo-qa> <MAAS:Expired> <https://launchpad.net/bugs/1707253>
[09:37] <sncder1> a
[11:14] <v92> Hi, I have multiple public subnets from which MAAS can allocate IP addresses. Is it possible to tell MAAS to pick subnet also because I don't care which subnet it will use ?
[12:25] <roaksoax> v92: if this is for a deployed node, you have to pick which subnet the interface gets an IP from
[12:54] <mup> Bug #1590689 changed: MAAS 1.9.3 + Juju 1.25.5 - on the Juju controller node eth0 and juju-br0 interfaces have the same IP address at the same time <juju> <maas>
 <juju:Won't Fix> <juju-core:Won't Fix> <juju-core 1.25:Won't Fix> <MAAS:Invalid> <ifenslave (Ubuntu):Confirmed> <https://launchpad.net/bugs/1590689>
[12:54] <mup> Bug #1709849 changed: juju bridge creation with MAAS provider ruins static routes on host <canonical-bootstack> <cpe-onsite> <curtin:New> <juju:Incomplete by wpk> <MAAS:Invalid> <https://launchpad.net/bugs/1709849>
[13:31] <v92> roaksoax: yea I know, I did it manually, but it might be nice option to pick any subnet from fabric-X
[14:18] <mup> Bug #1719895 opened: MAAS won't provision daily artful image (20170927) <cloud-init:New> <MAAS:New> <https://launchpad.net/bugs/1719895>
[14:36] <mup> Bug #1719895 changed: MAAS won't provision daily artful image (20170927) <cloud-init:New> <MAAS:New> <https://launchpad.net/bugs/1719895>
[14:52] <admin0> hi all... i setup MaaS and it shows the single disk in the system .. during deploy it says something like:   Logical volume "root", swap  created .. and then borks with   [Errno 6] No such device or address: '/dev/sda2'
[14:52] <admin0> where is the kickstart/disk setup stored
[15:02] <vogelc> I have 2.3.0(alpha 3)  installed.  Can anyone point me to where I can configure the dhcp 'option domain-name' to something other than 'maas'?  I cant get to my cloud-init because it can find the region controller.
[17:35] <vogelc> roaksoax: Is there anyway to use an ip for the cloud-config-url during boot, rather than host name?  Its in the boot arguments.
[17:40] <roaksoax> vogelc: that is automatically provided. If your rack controller maas_url setting is pointing to the DNS name, the machines need to be able to reach that DNS name. If not, it needs to be an IP
[17:46] <vogelc> roaksoax: where do I find if my " rack controller maas_url setting is pointing to the DNS name"?
[17:47] <roaksoax> vogelc: /etc/maas/rackd.conf
[18:25] <vogelc> roaksoax: thank you, using an IP fixed the issue.
[18:26] <roaksoax> vogelc: awesome!
[18:57] <mup> Bug #1719974 opened: The "Save and Add Another" button in the add machine form does not appear to work <MAAS:Incomplete> <https://launchpad.net/bugs/1719974>
[18:57] <mup> Bug #1719975 opened: Add machine form hangs until commissioning succeeds or fails <MAAS:Incomplete> <https://launchpad.net/bugs/1719975>
[18:57] <mup> Bug #1719978 opened: feature request: allow user to provide additional  installer config <internal> <MAAS:Triaged> <https://launchpad.net/bugs/1719978>