Set PXE class lease expiration to 30 seconds

Bug #1207102 reported by Adam Stokes
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
maas (Ubuntu)
Fix Released
High
Andres Rodriguez
Precise
Won't Fix
Undecided
Unassigned

Bug Description

[impact]

MAAS is failing to add all enlisted machines to DNS. There seems to be a sync issue between dhcp and dns during enlishting.

[test case]
+ Have MaaS 1.3 running
+ Boot machines to be controlled by MaaS and get MaaS to enlist them.
+ Go on MaaS WebUI and change ipmi data and click 'accept and commission'

[regression potential]
This is not a code change but a configuration modification. It is a documented option within the dhcp manual so I assume it's been tested through the normal means.

[additional]
Expected results:

subnet 192.168.134.0 netmask 255.255.255.0 {
       filename "pxelinux.0";
       option subnet-mask 255.255.255.0;
       option broadcast-address 192.168.134.255;
       option domain-name-servers 192.168.134.2;
       option routers 192.168.134.1;
       range dynamic-bootp 192.168.134.10 192.168.134.20;

        class "PXE" {
          match if substring (option vendor-class-identifier, 0, 3) = "PXE";
          default-lease-time 30;
          max-lease-time 30;
        }

}

May 3 15:18:30 maas2 dhcpd: DHCPDISCOVER from 52:54:00:f7:72:fe via eth0
May 3 15:18:31 maas2 dhcpd: DHCPOFFER on 192.168.134.11 to 52:54:00:f7:72:fe via eth0
May 3 15:18:33 maas2 dhcpd: Wrote 0 class decls to leases file.
May 3 15:18:33 maas2 dhcpd: Wrote 0 deleted host decls to leases file.
May 3 15:18:33 maas2 dhcpd: Wrote 0 new dynamic host decls to leases file.
May 3 15:18:33 maas2 dhcpd: Wrote 11 leases to leases file.
May 3 15:18:33 maas2 dhcpd: DHCPREQUEST for 192.168.134.11 (192.168.134.2) from 52:54:00:f7:72:fe via eth0
May 3 15:18:33 maas2 dhcpd: DHCPACK on 192.168.134.11 to 52:54:00:f7:72:fe via eth0

lease 192.168.134.11 {
  starts 5 2013/05/03 19:18:33;
  ends 5 2013/05/03 19:19:03;
  tstp 5 2013/05/03 19:19:03;
  cltt 5 2013/05/03 19:18:33;
  binding state free;
  hardware ethernet 52:54:00:f7:72:fe;
  uid "\001RT\000\367r\376";
}

description: updated
Revision history for this message
Adam Stokes (adam-stokes) wrote :
Changed in maas (Ubuntu):
assignee: nobody → Andres Rodriguez (andreserl)
importance: Undecided → High
Revision history for this message
Adam Stokes (adam-stokes) wrote :

So the debdiff was uploaded and referenced bug 1069570 after I marked that one invalid. So I guess we can dis-regard this one?

Revision history for this message
Andres Rodriguez (andreserl) wrote :

The changelog referenced other bug report, it really has fixed this one.

This bug was fixed in the package maas - 1.4+bzr1539+dfsg-0ubuntu2

---------------
maas (1.4+bzr1539+dfsg-0ubuntu2) saucy; urgency=low

  * debian/patches/04-dhcp-lease-conflict.patch:
    Sets expiry lease time to 30 seconds (LP: #1069570)
 -- Adam Stokes <email address hidden> Wed, 31 Jul 2013 15:40:06 -0400

Changed in maas (Ubuntu):
status: New → Fix Released
Revision history for this message
Adam Stokes (adam-stokes) wrote :

The precise version should contain this fix as well, could I get an eta when the next maas releases are going to be done?

Thanks!
Adam

Revision history for this message
Adam Stokes (adam-stokes) wrote :

Ping, would like to an eta when this fix will be pushed to Precise

Thanks!
Adam

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Uploaded to -proposed

Revision history for this message
Robie Basak (racb) wrote :

Removing this from ~ubuntu-sponsors as it looks like it's been uploaded to precise-proposed in 1.2+bzr1373+dfsg-0ubuntu1~12.04.3. Though the changelog entry refers to bug 1069570, it looks like it should have referred to this bug instead.

Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

Changed in maas (Ubuntu Precise):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.