[Bug 848072] Re: [oneiric] net-installer dhcp client fails with a DHCPDECLINE

[Jacob Strauss]

Yes, I do still see the same problem with the current kernel and initrd.

I also tried creating a VM here and pxe-booting it.  I do see the same
problem in the new VM.

The relevant portions of the dhcpd.conf for the new VM are as follows.
The dhcp server is an old CentOS box.

allow booting;
allow bootp;
option domain-name "qrclab.com";
option domain-name-servers 172.17.0.111,172.17.0.101;
default-lease-time 3600;
max-lease-time 7200;
get-lease-hostnames true;
authoritative;

subnet 172.18.0.0 netmask 255.255.255.0 {
   option routers 172.18.0.1;

   host dunsel {
        hardware ethernet 52:54:00:18:00:80;
        fixed-address dunsel;
        next-server 172.18.0.11;
        filename "/pxelinux.0";
   }
}

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netcfg in Ubuntu.
https://bugs.launchpad.net/bugs/848072

Title:
  [oneiric] net-installer dhcp client fails with a DHCPDECLINE

Status in “netcfg” package in Ubuntu:
  Confirmed

Bug description:
  Installing recent oneiric builds via the net installer images fails.  The first dhcp request to fetch the pxe boot image succeeds, as does the second before fetching a kickstart file.  
  The third and final time, however, fails with the client rejecting the lease with a DHCPDECLINE, repeating this over and over again.

  I first started seeing this problem somewhere after the alpha-3
  installer image, though I'm not sure exactly where.  The
  20101020ubuntu63 installer build fails.

  Tracing through /sbin/dhclient-script it looks like the call in
  BOUND|RENEW|REBIND|REBOOT) where it calls 'ip -4 addr add [..]' was
  failing with a File Exists response.  The old and new settings
  appeared identical, however.

  I managed to work around this by adding an unconditional call to 'ip
  -4 addr flush dev $interface' in /sbin/dhclient-script right after the
  call to set_hostname.  With this workaround, all proceeds as expected,
  though I'm not sure what the underlying problem is.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/848072/+subscriptions