Okay so what needs to be done to fix this issue is to order the subnets in the generated configuration where the ones without gateways come first and the ones with gateways follow. This causes isc-dhcp to work correctly. This might be an issue with shared-network because the order of the subnets can only go so far before the order of shared-network breaks it. That is to say if there are 2 shared networks each with 2 subnets and one of each have a gateway defined then one of the 4 will have an issue as the order in that case cannot be enforced.
Note for next-server: You also need to set next-server on each subnet to make sure that it can communicate back to the rack controller on that subnet. If not the PXE client will select the IP from where it recieved the DHCP response which can be a different subnet. I think it might be best to say you can only provide DHCP to subnets that a rack controller has an IP address in. Without it the machines will fail to PXE boot. Or we don't enforce it which is legal and might be a network configuration that the administrator wants, but might be surprising to other users of MAAS. -- 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
