[16:07] <mup> Bug #1834978 changed: [2.5] too many rndc reload during commissioning <sts> <MAAS:New> <bind9 (Ubuntu):New> <https://launchpad.net/bugs/1834978>
[16:13] <mup> Bug #1834978 opened: [2.5] too many rndc reload during commissioning <sts> <MAAS:New> <bind9 (Ubuntu):New> <https://launchpad.net/bugs/1834978>
[16:19] <mup> Bug #1834978 changed: [2.5] too many rndc reload during commissioning <sts> <MAAS:New> <bind9 (Ubuntu):New> <https://launchpad.net/bugs/1834978>
[16:25] <mup> Bug #1834978 opened: [2.5] too many rndc reload during commissioning <sts> <MAAS:New> <bind9 (Ubuntu):New> <https://launchpad.net/bugs/1834978>
[16:31] <mup> Bug #1834978 changed: [2.5] too many rndc reload during commissioning <sts> <MAAS:New> <bind9 (Ubuntu):New> <https://launchpad.net/bugs/1834978>
[16:34] <mup> Bug #1838663 opened: Bug with the power configuration of the maas controller <MAAS:New> <https://launchpad.net/bugs/1838663>
[19:48] <ryan> Hi there, I've working on debugging an issue with an installed MaaS instance at $WORKPLACE.  after upgrade to MaaS 2.6, it seems that the generated dhcpd.conf does not include the boot filename options for any other vlans/subnets outside of the one the MaaS vlan itself is in.
[19:49] <ryan> We manually modified the config and copied the bootfile options to another subnet section of the config and lo-and-behold, we finally saw a machine on that subnet succesfully PXE-boot.  I've scoured through the MaaS docs and google'd until my fingers bleed, maybe I've missed something.  Has anyone here seen a similar issue?
[19:51] <ryan> *outside of the one the MaaS server itself is in* first sentence should have read. apologies :/
[19:57] <ryan> from my backup of the /var/lib/maas directory before the update to 2.6, it seems that dhcpd.conf used to be generated with the boot filename options in the global part of dhcpd.conf.  now after update, it only generates the boot filename options in the subnet section that MaaS itself is in.
[20:58] <ltrager> ryan: I believe this is expected so devices on other vlans/subnets don't PXE boot when they shouldn't
[20:58] <ltrager> ryan: you could add a custom DHCP snippet to get them back
[20:58] <ltrager> ryan: if you think thats wrong please file a bug :)