[Bug 1196975] Re: ifupdown calling dhclient with -1 causes it to fail when dhcp server unavailable

[Sven Mueller]

Well, that would cover the first failure mode I described, but we experience the second one.
I don't see any workaround, apart from removing the -1 from the dhclient options.

I'm sorry, but this means that a _part_ of my report might be invalid
(though we think we saw that issue), but the other part is valid, unless
you can provide instructions how to not experience this issue.

When an interface is set to use dhcp and is set to an online state,
dhclient shouldn't give up retrying to renew a lease, but it does.

** Changed in: ifupdown (Ubuntu)
       Status: Invalid => New

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

Title:
  ifupdown calling dhclient with -1 causes it to fail when dhcp server
  unavailable

Status in “ifupdown” package in Ubuntu:
  New

Bug description:
  Present in the Precise version (0.7~beta2ubuntu8) at least:

  ifupdown is hardcoded to call dhclient with -1, which causes it to exit on the first failure.
  This can happen in two ways:
  1) Failure to bring up the interface if the dhcp server doesn't respond in time (default 60s).
  2) Failure to renew if the dhcp server was unavailable during a previous renewal try.

  This is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694541 as
  well, it seems.

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