I don't think this bug is really fixed. At least not in the versions
which are in precise: isc-hdcp-client=4.1.ESV-R4-0ubuntu5.2,
ifupdown=0.7~beta2ubuntu8.
The problem occurs, if a dhcp server is not availlable for some time.
Then dhclient will send one DHCP-REQUEST on ifup or lease renewal and
That's another bug and yes the intended fix didn't work in 12.04.
There's a test isc-dhcp in precise-proposed with the fix, we're expecting this
to land for 12.04.1.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in
** Description changed:
cloud-init's /etc/init/cloud-init-nonet.conf is configured to block
running of cloud-init.conf until static-network-up is emitted.
The point of that event was to wait until interfaces were all
configured, and thus the network available.
In practice, what
cloud-init (0.6.1-0ubuntu16) oneiric; urgency=low
* catch up with trunk at revision 439
* warn on failure to set hostname (LP: #832175)
* properly wait for all static interfaces to be up before
cloud-init runs (depends on fix in LP:# 838968).
* in DataSources NoCloud and OVF, do not
This bug was fixed in the package ifupdown - 0.7~alpha5.1ubuntu4
---
ifupdown (0.7~alpha5.1ubuntu4) oneiric; urgency=low
* invoke dhclient3 with '-1', meaning it should exit failure if it does
not receive a response in 60 seconds. (LP: #838968)
* fix the broken
I just uploaded, but wanted to put some evidence of this being fixed here.
On the system that was taking 45 seconds for dhcp (where we saw this bug) we
have:
$ ls -altr --full-time /run/network
total 4
-rw-r--r-- 1 root root 0 2011-09-02 15:46:56.877861983 -0400 ifup.lo
drwxr-xr-x 2 root
We also need to protect against ever actually *hitting* the dhclient
timeout during normal operation.
netcfg and network-manager already do their own dhcp timeout handling,
so only ifupdown is still affected. We should raise the default timeout
in dhclient, otherwise we just have interfaces that
** Branch linked: lp:ubuntu/isc-dhcp
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/838968
Title:
static-network-up event does not wait for interfaces to have an
address
To
This bug was fixed in the package isc-dhcp - 4.1.1-P1-17ubuntu8
---
isc-dhcp (4.1.1-P1-17ubuntu8) oneiric; urgency=low
* debian/patches/dhclient-safer-timeout.dpatch: Increase default
timeout to ensure we don't hit it. Closes LP: #838968.
-- Steve Langasek
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/838968
Title:
static-network-up event does not
** Branch linked: lp:~smoser/ubuntu/oneiric/ifupdown/lp838968
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/838968
Title:
static-network-up event does not wait for interfaces
11 matches
Mail list logo
