[14:17] <mup> Bug #1563337 opened: maas packages incorrectly purge things needed by packages not being removed <MAAS:New> <https://launchpad.net/bugs/1563337>
[14:38] <mup> Bug #1563349 opened: MAAS 1.9.1 unable to control HP BL460c <blocks-hwcert-server> <MAAS:New> <https://launchpad.net/bugs/1563349>
[14:50] <mup> Bug #1563365 opened: [2.0a4] maas-region-api bind9 options duplicated in options.inside.maas preventing bind to start <MAAS:Triaged> <https://launchpad.net/bugs/1563365>
[15:05] <mup> Bug #1563365 changed: [2.0a4] maas-region-api bind9 options duplicated in options.inside.maas preventing bind to start <MAAS:Triaged> <https://launchpad.net/bugs/1563365>
[15:08] <mup> Bug #1563365 opened: [2.0a4] maas-region-api bind9 options duplicated in options.inside.maas preventing bind to start <MAAS:Triaged> <https://launchpad.net/bugs/1563365>
[15:20] <mup> Bug #1563349 changed: MAAS 1.9.1 unable to control HP BL460c <blocks-hwcert-server> <MAAS:Invalid> <https://launchpad.net/bugs/1563349>
[15:35] <mup> Bug #1563349 opened: MAAS 1.9.1 unable to control HP BL460c <blocks-hwcert-server> <MAAS:Invalid> <https://launchpad.net/bugs/1563349>
[15:38] <mup> Bug #1563349 changed: MAAS 1.9.1 unable to control HP BL460c <blocks-hwcert-server> <MAAS:Invalid> <https://launchpad.net/bugs/1563349>
[16:11] <mup> Bug #1563409 opened: [2.0a4] 2.0 api is confused about its hash <MAAS:New> <https://launchpad.net/bugs/1563409>
=== hazmat_ is now known as hazmat
[17:45] <timello> folks, to prevent some nodes to get auto discovered by MaaS the ideal is to block them through dnsmasq manually
[17:45] <timello> is that right?
[18:08] <mup> Bug #1563483 opened: after reboot maas server shows "One cluster is not yet connected to the region" <MAAS:Incomplete> <https://launchpad.net/bugs/1563483>
[18:29] <mup> Bug #1563489 opened: [2.0] renaming an interface does not trigger dns updates <MAAS:New> <https://launchpad.net/bugs/1563489>
[19:05] <secate> Hi there. Is it possible to manually add VLAN interfaces to rack-controllers in MAAS 2.0 alphas? (currently using alpha4 from ppa/next)
[19:06] <secate> the discovered/automatic interfaces on my primary rack-controller are correct, but on my secondary only the parent interface that the VLAN interfaces are derived from is populated (ie: I have the parent interface, but no VLAN interfaces as there should be)
[19:07] <secate> the network configuration is the same as the primary apart from IP addressing (but in the same subnets)
[19:08] <roaksoax> secate: if you define those in /etc/network/interface, MAAS should automatically discover those... is that not the case ?
[19:08] <roaksoax> secate: maas won't auto-create interfaces for you, so if you add vlan interfaces on e/n/i, it should just work
[19:10] <secate> roaksoax: yeah, they are defined in e/n/i and are up and functional before installation of maas-rack-controller package
[19:11] <secate> roaksoax: e/n/i/ config is the same as primary rack-controller, but after installation of maas-rack-controller and joining it to the primary via dpkg-reconfigure, all interfaces are there except for the VLAN interfaces specifically
[19:12] <secate> roaksoax: and "maas <login> interfaces create-vlan <secondary_rack_system_id> vlan=<maas_vlan_id> parent=<parent_vlan_maas_interface_id>" returns "Not Found" with no other info
[19:13] <secate> (so far I have assumed that is because you cannot create interfaces on rack controllers in the same manner that you can for nodes)
[19:29] <roaksoax> secate: that's probably a bug
[19:29] <roaksoax> secate: you "can" create but the discovery process runs eveyr so often
[19:29] <roaksoax> mpontillo: ^^
[19:29] <roaksoax> seems like a critical bug
[19:29] <roaksoax> bladernr: ^^
[19:29] <roaksoax> errr
[19:29] <roaksoax> blake_r: ^^
[19:29] <roaksoax> bladernr: sry
[19:30] <bladernr> hehe, maybe I should change my nick to not_blake_r :D
[19:31] <blake_r> secate: please perform "sudo maas-rack support_dump" and file a bug
[19:31] <roaksoax> bladernr: :) 'b
[19:31] <roaksoax> bladernr: :) 'b-tab' :)
[19:31] <blake_r> secate: that will help us diagnose the issue and allow us to make sure we are handling your network configuration correctly
=== stormmore1 is now known as stormmore
[19:42] <mpontillo> support-dump with a - not a _
[19:45] <blake_r> secate: ^
[23:28] <mup> Bug #1563581 opened: tries to commission w/ trusty when only xenial images are available <MAAS:New> <https://launchpad.net/bugs/1563581>