[Bug 974284] Re: invoking dhclient3 with -1 causes issue if no dhcp server available

[Marc Deslauriers]

The patch to correct this issue never actually made it to precise, as it
got added at the end of the 00series file, which gets reverted during
build. Reopening.

** Changed in: isc-dhcp (Ubuntu)
       Status: Fix Released => Confirmed

** Also affects: isc-dhcp (Ubuntu Precise)
   Importance: Undecided
       Status: New

** Also affects: isc-dhcp (Ubuntu Quantal)
   Importance: High
     Assignee: Stéphane Graber (stgraber)
       Status: Confirmed

** Changed in: isc-dhcp (Ubuntu Precise)
       Status: New => Confirmed

** Changed in: isc-dhcp (Ubuntu Quantal)
       Status: Confirmed => Fix Released

** Changed in: isc-dhcp (Ubuntu Precise)
   Importance: Undecided => High

** Changed in: isc-dhcp (Ubuntu Precise)
     Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: isc-dhcp (Ubuntu Quantal)
     Assignee: Stéphane Graber (stgraber) => (unassigned)

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

Title:
  invoking dhclient3 with -1 causes issue if no dhcp server available

Status in “isc-dhcp” package in Ubuntu:
  Fix Released
Status in “isc-dhcp” source package in Precise:
  Confirmed
Status in “isc-dhcp” source package in Quantal:
  Fix Released

Bug description:
  In bug 838968, we modified ifupdown to invoke dhclient3 with '-1' as a
  parameter [1], and subsequently changed the default timeout of
  dhclient in isc-dhcp3 to from 60 seconds to 300 seconds [2].

  The reason for this is that we now have a reliable "static-networking-
  up" event that can be used for upstart jobs to start on, when static
  networking is up.  Here, static is any networking with an entry in
  /etc/network/interfaces.

  That event is used by cloud-init and other things that depend on
  network.

  The fallout of this is that if for some reason a server (or cloud-
  instance, or anything really), boots and does not obtain a dhcp
  address in 5 minutes, then it will give up forever.  The previous
  behavior is that it would try forever.

  This scenario isn't terribly unrealistic.  A power fail could take out
  a dchp server, cause a fsck, while the server came up 5 minutes before
  the dhcp server was up.

  Issue was originally raised in #openstack-dev by rmk around
  2012-04-05T06:42:19 [3]

  --
  [1] http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/ifupdown/precise/revision/56
  [2] http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/isc-dhcp/precise/revision/32
  [3] http://eavesdrop.openstack.org/irclogs/%23openstack-dev/%23openstack-dev.2012-04-05.log

  Releated bugs:
    * bug 838968: static-network-up event does not wait for interfaces to have an address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/974284/+subscriptions