1 MAC Address, two IPs - DNS is "out of sync" with DHCP leases databases
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Unassigned | ||
1.3 |
Fix Released
|
Critical
|
Julian Edwards | ||
juju-core |
Invalid
|
Undecided
|
Unassigned | ||
isc-dhcp (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Won't Fix
|
Undecided
|
Unassigned | ||
Raring |
Fix Released
|
Undecided
|
Unassigned | ||
Saucy |
Fix Released
|
Undecided
|
Unassigned | ||
maas (Ubuntu) |
Fix Released
|
High
|
Adam Stokes | ||
Precise |
Fix Released
|
Medium
|
Unassigned | ||
Raring |
Won't Fix
|
Undecided
|
Unassigned | ||
Saucy |
Fix Released
|
High
|
Adam Stokes |
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\
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\
}
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\
}
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-
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/
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
Related branches
- Julian Edwards (community): Approve
-
Diff: 11 lines (+1/-0)1 file modifiedsrc/provisioningserver/dhcp/config.py (+1/-0)
- Julian Edwards (community): Approve
-
Diff: 11 lines (+1/-0)1 file modifiedsrc/provisioningserver/dhcp/config.py (+1/-0)
summary: |
- DNS is out of "sync" with DHCP leases databases + 1 MAC Address, two IPs - DNS is out of "sync" with DHCP leases + databases, I think... |
summary: |
- 1 MAC Address, two IPs - DNS is out of "sync" with DHCP leases + 1 MAC Address, two IPs - DNS is "out of sync" with DHCP leases databases, I think... |
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → 12.10-stabilization |
Changed in maas (Ubuntu): | |
status: | New → Incomplete |
Changed in maas (Ubuntu): | |
status: | Expired → Incomplete |
description: | updated |
description: | updated |
Changed in maas (Ubuntu): | |
status: | Incomplete → Invalid |
information type: | Public → Public Security |
information type: | Public Security → Public |
Changed in maas: | |
status: | Triaged → Fix Released |
Changed in juju-core: | |
status: | New → Invalid |
Changed in maas (Ubuntu): | |
status: | Invalid → In Progress |
assignee: | nobody → Adam Stokes (adam-stokes) |
importance: | Undecided → Medium |
importance: | Medium → High |
Changed in maas (Ubuntu): | |
status: | In Progress → Invalid |
summary: |
- 1 MAC Address, two IPs - DNS is "out of sync" with DHCP leases - databases, I think... + 1 MAC Address, two IPs - DNS is "out of sync" with DHCP leases databases |
Changed in maas (Ubuntu Raring): | |
status: | Fix Released → Confirmed |
tags: |
added: verification-done removed: verification-needed |
I think I found something related to this problem...
After start enlisting my second node, I saw this on my syslog:
---
Oct 22 00:58:34 seed1 dhcpd: DHCPDISCOVER from 52:54:00:7a:58:42 via eth0
Oct 22 00:58:35 seed1 dhcpd: DHCPOFFER on 192.168.50.2 to 52:54:00:7a:58:42 via eth0
Oct 22 00:58:36 seed1 dhcpd: Can't create new lease file: Permission denied <- ### PROBLEM!!! ###
Oct 22 00:58:36 seed1 dhcpd: DHCPREQUEST for 192.168.50.2 (192.168.63.250) from 52:54:00:7a:58:42 via eth0
Oct 22 00:58:36 seed1 dhcpd: DHCPACK on 192.168.50.2 to 52:54:00:7a:58:42 via eth0
---
After couple reboots (I think 1 reboot) (before allocating it):
---
Oct 22 00:59:05 seed1 dhcpd: DHCPDISCOVER from 52:54:00:7a:58:42 via eth0
Oct 22 00:59:06 seed1 dhcpd: DHCPOFFER on 192.168.50.3 to 52:54:00:7a:58:42 (maas-enlist) via eth0
Oct 22 00:59:06 seed1 dhcpd: DHCPREQUEST for 192.168.50.3 (192.168.63.250) from 52:54:00:7a:58:42 (maas-enlist) via eth0
Oct 22 00:59:06 seed1 dhcpd: DHCPACK on 192.168.50.3 to 52:54:00:7a:58:42 (maas-enlist) via eth0
Oct 22 00:59:06 seed1 dhcpd: DHCPREQUEST for 192.168.50.3 (192.168.63.250) from 52:54:00:7a:58:42 (maas-enlist) via eth0
Oct 22 00:59:06 seed1 dhcpd: DHCPACK on 192.168.50.3 to 52:54:00:7a:58:42 (maas-enlist) via eth0
---
My node receive a new IP...
Looking forward into this...
Best,
Thiago