Ah, thanks for all the information. (I didn't realize you were pasting the kernel parameter.)
After researching this problem, I think this definitely looks like a bug in isc-dhcp. (The other possibility is that MAAS is configuring dhcpd incorrectly in this situation, but so far it looks like our configuration is correct, but dhcpd is interpreting it incorrectly.) I noticed that on Trusty we are using 4.2.4-7ubuntu12.3, while on Xenial we are using 4.3.1-5ubuntu4. 4.3.1-5ubuntu4. The latest "Extended support" version from ISC seems to be 4.3.3.[1] To move forward, we'll need to further triage this to see if the bug occurs on other versions of dhcpd. Meanwhile, I think you should be able to work around this issue by changing your hosts' network configuration after commissioning. You can configure MAAS to disable the boot interface upon deployment, so that your provisioning network will only be used for the initial PXE boot. [1]: https://www.isc.org/downloads/ ** Changed in: maas Status: Incomplete => Triaged ** Changed in: maas Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521618 Title: wrong subnet in DHCP answer when multiple networks are present To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1521618/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
