Red Hat Bugzilla – Bug 121817
install doesn't renew DHCP lease
Last modified: 2008-03-26 15:06:54 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;
Q312461; .NET CLR 1.1.4322)
Description of problem:
Installer hangs when doing FTP-installation because the DHCP lease is
not renewed properly during installation. My ISP drops the network
connection when the lease is not renewed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Connect computer to ISP which drops network connection when DHCP
lease is not renewed.
2. Try to install Fedora with FTP installation
Actual Results: Hanged installation
Expected Results: Flawless installation
I can confirm this bug in slightly different circumstances. If my case, the
installation was waiting for user input when the DHCP lease expired. The DHCP
server then gave the IP address to another computer. However, this computer
failed to boot because it noticed that the IP address was use. (The
half-installed box was presumably still responding to ARP requests for it's IP
address even though it hadn't renewed the lease.)
[This is a mass update sent to many bugs that missed earlier such messages due
to having their version set to a test version.]
This bug was originally filed against a version of Fedora Core which is no
longer supported, even for security updates. Many changes have occured since
then. Please retest this bug against a still supported version. Note that FC3
and FC4 are supported by Fedora Legacy for security fixes only. If
it still occurs on FC5 or FC6, please assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.
This bug will be closed after a few weeks if no information is given indicating
that the bug is still present in a supported release.
Bug still there during install of fc6.
Fedora Core 6 is no longer maintained.
Can you reproduce this bug in Fedora 8?
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.
Setting status to "INSUFFICIENT_DATA". If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.
Thank you in advance.