[04:02] <mup> Bug #1563581 changed: tries to commission w/ trusty when only xenial images are available <MAAS:New> <https://launchpad.net/bugs/1563581>
[09:42] <mup> Bug #1564802 opened: [2.0a4] cli maas boot-resources import does not trigger import <cdo-qa> <MAAS:New> <https://launchpad.net/bugs/1564802>
[13:16] <mup> Bug #1562142 changed: maas assigns wrong address if node is deleted and then re-deployed <MAAS:New> <https://launchpad.net/bugs/1562142>
[13:46] <mup> Bug #1564904 opened: MaaS is creating inconsistent name for mpath device <MAAS:New> <https://launchpad.net/bugs/1564904>
[13:46] <mup> Bug #1564908 opened: [2.0a4] Unknown power errors are vague <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1564908>
[13:52] <mup> Bug #1564904 changed: MaaS is creating inconsistent name for mpath device <MAAS:New> <https://launchpad.net/bugs/1564904>
[13:52] <mup> Bug #1564908 changed: [2.0a4] Unknown power errors are vague <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1564908>
[13:58] <mup> Bug #1564904 opened: MaaS is creating inconsistent name for mpath device <MAAS:New> <https://launchpad.net/bugs/1564904>
[13:58] <mup> Bug #1564908 opened: [2.0a4] Unknown power errors are vague <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1564908>
[14:16] <mup> Bug #1564904 changed: MaaS is creating inconsistent name for mpath device for ppc64el <curtin:New> <MAAS:Invalid> <https://launchpad.net/bugs/1564904>
[14:16] <mup> Bug #1564925 opened: [2.0] dhcp6 configuration is broken: expects CIDR not netmask <MAAS:New> <https://launchpad.net/bugs/1564925>
[14:16] <mup> Bug #1564927 opened: [2.0] Can't start OMAPI protocol: address not available <MAAS:New> <https://launchpad.net/bugs/1564927>
[15:47] <mup> Bug #1564971 opened: duplicate ipranges cuase dhcpd Configuration file errors <cdo-qa> <MAAS:New> <https://launchpad.net/bugs/1564971>
[16:17] <mup> Bug #1564977 opened: ppc64el 1.9.1 tries and fails sgdisk on the wrong device <uosci> <curtin:New> <MAAS:Incomplete> <https://launchpad.net/bugs/1564977>
[16:47] <mup> Bug #1564996 opened: [2.0a4] Rack controller makes a state transition when it shouldn't <MAAS:Triaged> <https://launchpad.net/bugs/1564996>
[17:44] <mup> Bug #1565016 opened: [2.0a4] Xenial deploy boot-initrd timeout and kernel panic <cdo-qa> <deploy> <xenial> <MAAS:New> <https://launchpad.net/bugs/1565016>
[18:43] <tim2> Hello all. Does anyone know if you can set up MAAS nodes to have DHCP/DNS managed through MASS controller on NIC1 but all other traffic (including internet) out NIC 2? It seems to be trying to send internet traffic out NIC1.
[18:48] <roaksoax> tim2: you can. You need to the machine you are deploying which subnect/interface to use as the default gateway
[18:48] <roaksoax> tim2: you can do that per node
[18:48] <roaksoax> tim2: only on 1.9+
[18:50] <tim2> Thank you roak. I do have 1.9.1 installed, and I did find on the node page where I can set eth1 to obtain an IP via DHCP, but I didn't see a place to set default gateway.
[18:55] <roaksoax> tim2: you can do this per node with: maas admin interface set-default-gateway <system_id> <interface_id>
[18:55] <roaksoax> where systemd_id is the ID of the node
[18:55] <roaksoax> and interface_id the id of the interface on that node
[18:59] <mup> Bug #1565016 changed: [2.0a4] Xenial deploy boot-initrd timeout and kernel panic <cdo-qa> <deploy> <xenial> <maas-images:New> <https://launchpad.net/bugs/1565016>
[20:47] <fvdf> kaaanker
[20:47] <fvdf> cancer
[22:31] <maaku> is there a list of the ports used for each component of MAAS?
[22:31] <maaku> I need to figure out how to configure my firewall..
[22:57] <mup> Bug #1565139 opened: Service 'maas-proxy' failed to reload: sudo: no tty present and no askpass program specified <MAAS:New> <https://launchpad.net/bugs/1565139>
[23:54] <mup> Bug #1557334 changed: [1.9.1]  Vfat & FAT32 Issues <curtin:Incomplete> <https://launchpad.net/bugs/1557334>