Comment 5 for bug 1639332
Revision history for this message
| Bert JW Regeer (bregeer-ctl) wrote Re: Expire the DHCP lease after commissioning or make the default-lease-time configurable | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
@andres:
The behavior I am seeing is not what you are telling me it should be. It never seems to time out the lease.
Here is what I am seeing:
1. Host boots, gets IP from the dynamic range
2. MaaS sets this IP as Observed
3. Node finishes enlisting
4. Node shuts down
5. IP stays as "Observed" in what seems like perpetuity (I waited 15+ minutes)
6. Other nodes that couldn't get an DHCP address don't PXE boot and don't enlist.
Now, as soon as I commission the nodes, the IP's get removed from Observed and yes, MaaS assigns a "static" IP.
At that point my remaining hosts enlisted without issues.
Unfortunately journalctl doesn't have information back to when I was trying to troubleshoot this, I tried the following:
1. Remove the leases files from /var/lib/
2. Restart maas-dhcpd
3. Watch node attempt to PXE boot, but it would log that no leases were available
I was discussing this with @roaksoax on IRC, apparently ISC-DHCP is supposed to notify MaaS, so removing the leases file should have cleared the leases that ISC knew about and it should have let the new nodes enlist. Does MaaS somehow notify DHCP about the existing "Observed" entries?