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

[Brian Murray]

Hello Thiago, or anyone else affected,

Accepted maas into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/maas/1.2+bzr1373+dfsg-
0ubuntu1~12.04.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: isc-dhcp (Ubuntu Precise)
   Importance: Undecided
       Status: New

** Also affects: maas (Ubuntu Precise)
   Importance: Undecided
       Status: New

** Changed in: maas (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: maas (Ubuntu Precise)
       Status: New => Triaged

** Changed in: maas (Ubuntu Precise)
       Status: Triaged => Fix Committed

** Tags added: verification-needed

-- 
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

Status in juju-core:
  Invalid
Status in MAAS:
  Fix Released
Status in MAAS 1.3 series:
  Fix Released
Status in “isc-dhcp” package in Ubuntu:
  Fix Released
Status in “maas” package in Ubuntu:
  Fix Released
Status in “isc-dhcp” source package in Precise:
  New
Status in “maas” source package in Precise:
  Fix Committed
Status in “isc-dhcp” source package in Raring:
  Fix Released
Status in “maas” source package in Raring:
  Confirmed
Status in “isc-dhcp” source package in Saucy:
  Fix Released
Status in “maas” source package in Saucy:
  Fix Released

Bug description:
  [Impact] 
   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:

  # The format of this file is documented in the dhcpd.leases(5) manual page.
  # This lease file was written by isc-dhcp-4.2.4

  server-duid "\000\001\000\001\030\023\243\007RT\000\360\236\231";

  lease 192.168.50.1 {
    starts 5 2012/10/19 06:31:21;
    ends 5 2012/10/19 18:31:21;
    cltt 5 2012/10/19 06:31:21;
    binding state active;
    next binding state free;
    rewind binding state free;
    hardware ethernet 52:54:00:cd:6b:a2;
    uid "\001RT\000\315k\242";
  }
  lease 192.168.50.2 {
    starts 5 2012/10/19 06:31:43;
    ends 5 2012/10/19 18:31:43;
    cltt 5 2012/10/19 06:31:43;
    binding state active;
    next binding state free;
    rewind binding state free;
    hardware ethernet 52:54:00:cd:6b:a2;
    client-hostname "maas-enlist";
  }
  lease 192.168.50.2 {
    starts 5 2012/10/19 06:31:43;
    ends 5 2012/10/19 18:31:43;
    cltt 5 2012/10/19 06:31:43;
    binding state active;
    next binding state free;
    rewind binding state free;
    hardware ethernet 52:54:00:cd:6b:a2;
    client-hostname "maas-enlist";
  }
  host 192.168.50.1 {
    dynamic;
    hardware ethernet 52:54:00:cd:6b:a2;
    fixed-address 192.168.50.1;
  }
  lease 192.168.50.1 {
    starts 5 2012/10/19 06:31:21;
    ends 5 2012/10/19 06:34:48;
    tstp 5 2012/10/19 06:34:48;
    cltt 5 2012/10/19 06:31:21;
    binding state free;
    hardware ethernet 52:54:00:cd:6b:a2;
    uid "\001RT\000\315k\242";
  }

   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...

  [Test Case]
  In a virtual environment: 
  - Add 2 nodes 
  - PXE boot the instances
  - verify dhcp leases have 1 mac address for 2 different IPs

  After applying latest debdiff alter the following:

     * modify /etc/maas/dhcpd.conf to include 'ignore-client-uids true'

  re-test by adding 2 additional nodes to verify the mac address is
  unique between both nodes.

  [Regression Potential]
  Low, as it adds another optional arguement to disable checking client-uids

  -- snip --

   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