Comment 32 for bug 1707999

Revision history for this message
Jason Hobbs (jason-hobbs) wrote : Re: pod VM fails to PXE boot after receiving multiple DHCP offers from both primary and secondary rack controllers, for different IPs

In the pastebin from comment #31, the 10.245.209.7 address comes from the host entry maas is creating in dhcpd.conf. The entry gets created on both the primary and secondary server. Perhaps if it's there, the server will respond, even if it's secondary?

The next question is why the primary dhcp server didn't offer 10.245.209.7 (the auto assigned IP) during the "second pxe boot" - when the node was booting to deploy. It instead offered 10.245.208.168 and added a lease entry for it:

http://paste.ubuntu.com/25617392/

I wonder if for some reason its dhcpd.conf hadn't been rewritten with the host entry for 52:54:00:af:49:b8?