[11:01] <mup> Bug #1728891 opened: [2.3b3, UI] In Pods, the composed machine column header works only once for sorting the column  <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1728891>
[11:01] <mup> Bug #1728893 opened: Add an RDS Pod with an invalid address by clicking on Add Pod and then nothing happens <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1728893>
[11:31] <mup> Bug #1728894 opened: [2.3b3, UI] When I try to refresh pods in pod listing and there is an error, there is no error text in the table <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1728894>
[11:31] <mup> Bug #1728899 opened: when Comissioning a node, the grub command line apppear  <grub> <MAAS:New> <https://launchpad.net/bugs/1728899>
[12:17] <mup> Bug #1728909 opened: Maas Settings tab encountered an issue <MAAS:New> <https://launchpad.net/bugs/1728909>
[15:11] <mup> Bug #1703686 changed: Rack controller disconnects when the regiond process can't find self in database. <registration> <MAAS:Invalid> <MAAS 2.2:Invalid> <https://launchpad.net/bugs/1703686>
[15:11] <mup> Bug #1719669 changed: pod VM fails commissioning; requests pxelinux.0 but doesn't progress past that <cdo-qa> <cdo-qa-blocker> <foundations-engine> <internal> <MAAS:Invalid by jason-hobbs> <https://launchpad.net/bugs/1719669>
[15:26] <mup> Bug #1721611 changed: [2.3] Rack refresh failures may be causing controllers to become degraded <MAAS:Invalid> <https://launchpad.net/bugs/1721611>
[15:26] <mup> Bug #1722620 changed: [2.3, HA] Failed to update regiond's process and endpoints; records may be out of date <MAAS:Fix Released> <https://launchpad.net/bugs/1722620>
[15:26] <mup> Bug #1719669 opened: pod VM fails commissioning; requests pxelinux.0 but doesn't progress past that <cdo-qa> <cdo-qa-blocker> <foundations-engine> <internal> <MAAS:Invalid by jason-hobbs> <https://launchpad.net/bugs/1719669>
[15:56] <mup> Bug # changed: 1586006, 1659379, 1680632, 1722609
[16:46] <shadoxx> Has anyone configured KVM on the Maas controller before? I'm trying to get Maas to manage power in the KVM guests, but I can't figure out how the virsh console works when virsh is installed locally
[16:46] <shadoxx> IE, kvm and maas are installed in the same OS
[16:46] <shadoxx> and on the same hardware. the virsh address would be localhost, but it's not working...
[16:50] <shadoxx> oh, i'm running it on the incorrect host
[16:50] <shadoxx> whoops
[20:33] <Charlie> Hi, MAAS Noob needing some troubleshooting help, google gave me very little. Anyone able to spare a few mins to lend a hand?
[21:14] <bdx> Hello,
[21:14] <bdx> how can I make a node get dns on all of its interface ips?
[21:14] <bdx> or at least make it deterministic, which network gets the dns
[21:17] <bdx> or make it get dns on the subnet that I want it to get dns on?
[21:51] <roaksoax> bdx: ohw is your maas configured? or your machine rather?
[21:51] <roaksoax> which dns does it currently get ?
[22:01] <bdx> roaksoax: https://imgur.com/a/JqwK0
[22:01] <bdx> https://imgur.com/a/CEBll
[22:14] <roaksoax> bdx: right, so what dns does the machine get when deployed ? from the auto assign or the DHCP interface ?
[22:14] <bdx> roaksoax: auto-assign
[22:15] <roaksoax> bdx: so that seems correct then
[22:15] <roaksoax> bdx: what address do you want it to get ?
[22:17] <bdx> roaksoax: I want the nodes to get dns on the interface/subnet that they have a gateway on
[22:17] <bdx> or, my colleagues do
[22:18] <bdx> I told them to stop worrying about what the node's ips are, now they are needing dns :)
[22:20] <roaksoax> bdx: right, so your node configuration is only being configured against 1 subnet
[22:20] <roaksoax> hence, the machine turns out with 1 DNS server configured
[22:21] <roaksoax> bdx: if you were to have interface sin other subnets, the machine would be configured with the DNS of those other subnets
[22:21] <roaksoax> bdx: if you want to override, you can input DNS servers for a specific subnet
[22:21] <roaksoax> e.g. in 192.168.20.0/24 you can add "DNS Servers" fr that subnet
[22:22] <bdx> roaksoax: got it, then give the nodes static ips in maas and staticly define them in the dns too then?
[22:22] <bdx> ok
[22:22] <bdx> I see
[22:23] <bdx> roaksoax: can I choose to have dns on 10.10.0.1/16 instead of 192.168.20.0/24?
[22:23] <bdx> or why is it on 192.168.20.0/24 even?
[22:24] <bdx> the node has interfaces on both of those flat networks (switch ports in access mode for each vlan/subnet)
[22:24] <bdx> maas manages both of those subnets
[22:25] <bdx> and a bunch of other subnets
[22:25] <bdx> and it just choose 192.168.20.0/24?
[22:25] <bdx> to manage dns on
[22:27] <roaksoax> bdx: no, so say, you you have 1 machine with 2 auto assign IP's
[22:27] <roaksoax> bdx: maas should give you the default dns it automaticaly picks for those subnets, which would be MAAS itself
[22:27] <roaksoax> so if you want to override that behavior
[22:28] <roaksoax> then you would go to the subnets and input your own DNS for those subnets
[22:28] <roaksoax> bdx: so you, if say you only want DNS on .20.0/24 you can override that on the subnet by inputting the DNS servers you want there
[22:29] <bdx> roaksoax: ok, got it
[22:29] <bdx> so, possibly I'm viewing how maas manages dns incorrectly then
[22:30] <bdx> roaksoax: maas only manages dns for auto-assign type interface configurations?
[22:30] <bdx> so, its not the subnet then, its the interface IP Address configuration that determines if dns is managed there
[22:31] <bdx> and interface IP Address configured to dhcp, does not get managed dns from maas
[22:39] <roaksoax> bdx: for everything, it will configure the same subnet dns on isc-dhcp
[22:40] <roaksoax> bdx: maybe then via the default gateway ?
[22:40] <roaksoax> bdx: that may be it instead, I do remember changed the behavior to address various issues came across
[22:40] <roaksoax> it may be based on the machine that has the default gateway
[22:40] <roaksoax> unless overriden in the subnet
[22:40] <bdx> roaksoax: the only gateway I have is on the 10.10.0.0/16
[22:41] <bdx> ooh as far as maas is concerned
[22:41] <bdx> in the subnet configuration?
[22:41] <bdx> the gateway config
[22:41] <bdx> ooooooh
[22:41] <bdx> I bet thats it
[22:42] <bdx> so, the gateway is set on both of those subnets
[22:42] <bdx> but one of them, the 192.168.20.0/24 net's gateway is maas
[22:43] <bdx> the 10.10.0.0/16 net has an upstream gateway
[22:43] <bdx> like at the top of the rack or whatever
[22:44] <bdx> roaksoax: I will try removing the gateway config for the 192.168.20 net and see if the  10.10.0 net gets dns when I next deploy
[22:54] <bdx> roaksoax: removing the gateway from the 192.168.20.0/24 net caused the node to get dns on the 10.10.0.0/16 net
[22:55] <bdx> roaksoax: many thanks
[22:55] <bdx> I didn't need to have a gateway defined there anyway
[22:56] <bdx> roaksoax: it would be cool if that was a more deterministic process though
[23:08] <bdx> well
[23:08] <bdx> roaksoax: I have a node that just got dns on 192.168.20.0 http://paste.ubuntu.com/25861769/
[23:11] <bdx> and now a few moments later, the dns points at the node's 10.10.0.0/16 interface http://paste.ubuntu.com/25861782/
[23:11] <bdx> given, its currently deploying
[23:11] <bdx> but still