| 2012-04-05 13:55:59 |
Scott Moser |
bug |
|
|
added bug |
| 2012-04-05 14:33:30 |
Scott Moser |
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.
--
[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
Releated bugs:
* bug 838968: static-network-up event does not wait for interfaces to have an address |
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. It 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 |
|
| 2012-04-05 14:33:56 |
Scott Moser |
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. It 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 |
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 |
|
| 2012-04-05 16:52:39 |
Steve Langasek |
ifupdown (Ubuntu): assignee |
|
Stéphane Graber (stgraber) |
|
| 2012-04-05 16:54:30 |
Steve Langasek |
affects |
ifupdown (Ubuntu) |
isc-dhcp (Ubuntu) |
|
| 2012-04-05 16:54:30 |
Steve Langasek |
isc-dhcp (Ubuntu): importance |
Undecided |
High |
|
| 2012-04-05 16:54:30 |
Steve Langasek |
isc-dhcp (Ubuntu): assignee |
Stéphane Graber (stgraber) |
|
|
| 2012-04-05 16:54:59 |
Steve Langasek |
isc-dhcp (Ubuntu): assignee |
|
Stéphane Graber (stgraber) |
|
| 2012-04-05 17:02:38 |
Launchpad Janitor |
isc-dhcp (Ubuntu): status |
New |
Confirmed |
|
| 2012-04-10 18:07:42 |
Launchpad Janitor |
isc-dhcp (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2012-07-25 21:43:52 |
Marc Deslauriers |
isc-dhcp (Ubuntu): status |
Fix Released |
Confirmed |
|
| 2012-07-25 21:44:03 |
Marc Deslauriers |
nominated for series |
|
Ubuntu Precise |
|
| 2012-07-25 21:44:03 |
Marc Deslauriers |
bug task added |
|
isc-dhcp (Ubuntu Precise) |
|
| 2012-07-25 21:44:03 |
Marc Deslauriers |
nominated for series |
|
Ubuntu Quantal |
|
| 2012-07-25 21:44:03 |
Marc Deslauriers |
bug task added |
|
isc-dhcp (Ubuntu Quantal) |
|
| 2012-07-25 21:44:24 |
Marc Deslauriers |
isc-dhcp (Ubuntu Precise): status |
New |
Confirmed |
|
| 2012-07-25 21:44:26 |
Marc Deslauriers |
isc-dhcp (Ubuntu Quantal): status |
Confirmed |
Fix Released |
|
| 2012-07-25 21:44:29 |
Marc Deslauriers |
isc-dhcp (Ubuntu Precise): importance |
Undecided |
High |
|
| 2012-07-25 21:44:35 |
Marc Deslauriers |
isc-dhcp (Ubuntu Precise): assignee |
|
Stéphane Graber (stgraber) |
|
| 2012-07-25 21:44:39 |
Marc Deslauriers |
isc-dhcp (Ubuntu Quantal): assignee |
Stéphane Graber (stgraber) |
|
|
| 2012-07-27 14:16:18 |
Stéphane Graber |
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 |
[rational]
A patch was designed to fix this bug back in precise but because of where it was put in debian/patches/00list it was actually being reverted at build time and so never fixing that bug.
In quantal, the reverting code in debian/rules is now gone, so it's been applied ever since the 4.2 merge, so far without hearing any problem with it.
[test case]
1) Start dhclient -1 <interface> on a working network
2) Unplug the network cable or stop the DHCP server
3) Wait for the lease to expire
4) Check that dhclient tries to get a new lease and when failing, keeps trying
The original behaviour of -1 would make 4) try just a single time, then give up, causing dhclient to remove all addresses and exit on a machine that was unable to reach its dhcp server for >= expiry.
[regression potential]
This change is definitely causing a slight change in behaviour, though based on this bug report and others, it's believe to be the wanted behaviour of -1 for most of our users.
The change itself has been applied to quantal without any regression and was tested on 12.04 in the past (before I messed up the ordering in the final upload ...).
The code change itself just makes "-1" use the same renewal behaviour as when called without "-1" (but still follows the standard "-1" behaviour for the first request).
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 |
|
| 2012-08-01 19:29:59 |
Clint Byrum |
isc-dhcp (Ubuntu Precise): status |
Confirmed |
Fix Committed |
|
| 2012-08-01 19:30:01 |
Clint Byrum |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2012-08-01 19:30:06 |
Clint Byrum |
bug |
|
|
added subscriber SRU Verification |
| 2012-08-01 19:30:08 |
Clint Byrum |
tags |
|
verification-needed |
|
| 2012-08-01 19:47:19 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/precise-proposed/isc-dhcp |
|
| 2012-08-13 02:46:15 |
Stéphane Graber |
tags |
verification-needed |
verification-failed |
|
| 2012-08-13 02:47:33 |
Stéphane Graber |
isc-dhcp (Ubuntu Precise): status |
Fix Committed |
Triaged |
|
| 2012-08-13 02:47:35 |
Stéphane Graber |
isc-dhcp (Ubuntu Quantal): status |
Fix Released |
Triaged |
|
| 2012-08-13 02:47:38 |
Stéphane Graber |
isc-dhcp (Ubuntu Quantal): assignee |
|
Stéphane Graber (stgraber) |
|
| 2012-09-12 21:50:12 |
Launchpad Janitor |
isc-dhcp (Ubuntu Quantal): status |
Triaged |
Fix Released |
|
| 2012-09-17 14:45:57 |
Stéphane Graber |
isc-dhcp (Ubuntu Precise): status |
Triaged |
Fix Committed |
|
| 2012-09-17 14:46:00 |
Stéphane Graber |
isc-dhcp (Ubuntu Precise): status |
Fix Committed |
In Progress |
|
| 2012-11-07 22:52:24 |
Clint Byrum |
isc-dhcp (Ubuntu Precise): status |
In Progress |
Fix Committed |
|
| 2012-11-07 22:52:30 |
Clint Byrum |
tags |
verification-failed |
|
|
| 2012-11-07 22:52:32 |
Clint Byrum |
tags |
|
verification-needed |
|
| 2013-01-24 23:25:53 |
Stéphane Graber |
tags |
verification-needed |
verification-done |
|
| 2013-01-25 00:32:13 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2013-01-25 00:32:13 |
Launchpad Janitor |
isc-dhcp (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
| 2013-03-05 17:10:46 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/raring/isc-dhcp/nouid |
|
| 2013-04-29 16:54:24 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/precise/isc-dhcp/precise-updates.dist |
|
