[Bug 1069570] Re: 1 MAC Address, two IPs - DNS is "out of sync" with DHCP leases databases, I think...

[Robert Ayres]

To update the ticket, I've reproduced using 12.10 KVM machines (have
attached tcpdump and leases file as requested).

As described previously, iPXE gets a different IP address to the OS
image. Seems iPXE sends a DHCP client-id parameter and the OS doesn't.
The current version of isc-dhcp-server (4.2.4-1ubuntu10.1) treats each
as a different request.

Unfortunately, I haven't found a way to stop iPXE sending a client-id parameter.
However, you can add the following PPA to your MAAS server:

https://launchpad.net/~virtual-maasers/+archive/maas-updated-packages

which contains a patched DHCP server.
Updating to this, editing /etc/maas/dhcpd.conf to add the 'ignore-client-uids true;' to the subnet declaration, then restarting the MAAS DHCP server will fix the problem - client-ids will be ignored when assigning addresses.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1069570

Title:
  1 MAC Address, two IPs - DNS is "out of sync" with DHCP leases
  databases, I think...

Status in juju-core:
  New
Status in MAAS:
  Triaged
Status in “isc-dhcp” package in Ubuntu:
  Confirmed
Status in “maas” package in Ubuntu:
  Incomplete

Bug description:
  Guys,

   During my new tests, I tried to create two nodes simultaneously (both
  via DHCP + PXE, not by clicking "+Add node") and I hit this problem:

   Same MAC Address, two different IPs:

   http://pastebin.com/8RYjGe5D

   The brief is:

   1- DHCP gives address 192.168.50.1 to my machine on its first boot;

   2- After some time, I think that after some "reboots / elist /
  don'know for sure or even after commissioning" it; the IP have changed
  to 192.168.50.2 and got registered at DNS (192-168-50-2.test.com) that
  way;

   3- In the end of the day, after allocate it to root and start using
  it (the nodes), the DHCP gives again the IP 192.168.50.1 to my node,
  but DNS still remains with 192.158.50.2...

   ---

   My second node, first starts with 192.168.50.3, got registered with
  192.168.50.4 at DNS (and at MaaS Web GUI) but the DHCP finish with
  192.168.50.3...

   I'll not try maas-dns again... Too many bugs...   =(

   I think that MaaS needs some kind of "glue" between DHCP and DNS to
  keep it in sync.

  Tks!
  Thiago

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1069570/+subscriptions