Comment 58 for bug 1069570

Revision history for this message
Matt Rae (mattrae) wrote :

I see for precise-proposed, the patch is to add a 30 second lease for pxe agents. This is resulting the lease during pxe being added to the leases file with a 30 second expiration as expected, but the expiration is not being honored.

We are seeing machines given the ip from the 30 second lease long after it had expired.

It appears dhcpd is not respecting the 30 second lease and still giving the wrong ip to nodes.

Example:

Below are the leases for a machine that came up with the wrong ip. The lease for 172.21.66.24 is supposed to be for 30 seconds, but it appears it was not being respected, since the node would come up with .24 after rebooting long after the lease should be expired.

host 172.21.66.24 {
  dynamic;
  hardware ethernet 52:54:00:e3:1d:47;
  fixed-address 172.21.66.24;
}
lease 172.21.66.24 {
  starts 4 2013/09/05 01:40:28;
  ends 4 2013/09/05 01:40:58;
  tstp 4 2013/09/05 01:40:58;
  cltt 4 2013/09/05 01:40:28;
  binding state free;
  hardware ethernet 52:54:00:e3:1d:47;
  uid "\001RT\000\343\035G";
}
lease 172.21.66.29 {
  starts 4 2013/09/05 01:40:40;
  ends 4 2013/09/05 13:40:40;
  tstp 4 2013/09/05 13:40:40;
  cltt 4 2013/09/05 01:40:40;
  binding state active;
  next binding state free;
  hardware ethernet 52:54:00:e3:1d:47;
  client-hostname "maas-enlist";
}