[Bug 1189571] Re: [SRU] "Unable to set up timer: out of range" caused by bad 64_bit timer
Brian Murray
brian at ubuntu.com
Thu Jun 13 21:54:03 UTC 2013
Hello Ben, or anyone else affected,
Accepted isc-dhcp into raring-proposed. The package will build now and
be available at http://launchpad.net/ubuntu/+source/isc-
dhcp/4.2.4-5ubuntu2.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: isc-dhcp (Ubuntu Raring)
Status: Confirmed => Fix Committed
** Tags added: verification-needed
** Changed in: isc-dhcp (Ubuntu Quantal)
Status: Confirmed => Fix Committed
--
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/1189571
Title:
[SRU] "Unable to set up timer: out of range" caused by bad 64_bit
timer
Status in DHCP:
Unknown
Status in “isc-dhcp” package in Ubuntu:
Fix Released
Status in “isc-dhcp” source package in Quantal:
Fix Committed
Status in “isc-dhcp” source package in Raring:
Fix Committed
Status in “isc-dhcp” source package in Saucy:
Fix Released
Status in “isc-dhcp” package in Fedora:
Unknown
Bug description:
SRU justification
[Symtpom]:The dchp client on 12.10 and 13.04 on 64-bit installations
fails with "Unable to set up timer: out of range" and then exits when
the max lease time is given (~135years).
[Impact]: Systems running on networks with max lease times will not
configure and the dhcpclient will error out and exit.
[Test Case]:
- Set DHCP Server to serve out max lease times
- Configure Ubuntu to use DHCP
- Run "sudo restart networking"
- Check if dhclient is NOT running, i.e. "ps axw | grep dhclient"
- Install new isc-dhcp-client and isc-dhcp-common package
- Run "sudo restart networking"
- Check if dhclient IS running, i.e. "ps axw | grep dhclient"
[Regression]: No regressions are expected. This fix simply reduces the
lease time to (MAX_TIME - 9) seconds in cases where the lease exceeds
the max lease.
[Other Info]
This is an upstream regression between 4.1.ESV-R4 (precise's isc-dhcp) and 4.2.4 (quantal, raring, saucy). It was fixed in Fedora under redhat bug 789601 (http://pkgs.fedoraproject.org/cgit/dhcp.git/commit/?id=bd413ec3f9585ff8ccb8a5a66097fab53a8f5fe4)
[Originial Report]:
On Windows Azure, the max lease time is used. In digging, it appears
that the problem is related to the large lease times:
From /var/log/upstart/netwokring:
Listening on LPF/eth0/00:15:5d:52:cd:db
Sending on LPF/eth0/00:15:5d:52:cd:db
Sending on Socket/fallback
DHCPREQUEST of 100.86.20.3 on eth0 to 255.255.255.255 port 67 (xid=0x30df9c2d)
DHCPACK of 100.86.20.3 from 100.86.20.1
RTNETLINK answers: File exists
Unable to set up timer: out of range
Failed to bring up eth0.
This looks like a duplicate of the RH Bug 789601
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: isc-dhcp-client 4.2.4-5ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
Uname: Linux 3.8.0-23-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Mon Jun 10 17:57:48 2013
MarkForUpload: True
SourcePackage: isc-dhcp
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/dhcp/+bug/1189571/+subscriptions
More information about the foundations-bugs
mailing list