Red Hat Bugzilla – Bug 641324
IPV4 DHCP configuration is always used in stage 2 network enablement if DHCP server is present.
Last modified: 2011-05-19 08:52:00 EDT
+++ This bug was initially created as a clone of Bug #640951 +++
Created attachment 452081 [details]
patch with fix
Description of problem:
If the network is enabled in stage 2, IPV4 DHCP instead of configuration set in nm-c-e.
Version-Release number of selected component (if applicable):
Fedora 14 Beta,
Steps to Reproduce:
1. Start DVD install
2. Enable Fedora 14 Beta repo in repository UI screen
3. Configure static networking in nm-c-e.
4. look at ifconfig in tty2 - dhcp was used
IPv4 DHCP is used.
Configuration set in nm-c-e is used
Attaching tested patch
--- Additional comment from email@example.com on 2010-10-08 07:24:05 EDT ---
Proposing as F14 Blocker with hope for Nice To Have.
The patch in master:
(In reply to comment #0)
> Steps to Reproduce:
> 1. Start DVD install
> 2. Enable Fedora 14 Beta repo in repository UI screen
> 3. Configure static networking in nm-c-e.
> 4. look at ifconfig in tty2 - dhcp was used
> Actual results:
> IPv4 DHCP is used.
If dhcp configuration doesn't fail (i.e. there actually is a DHCP server on the
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update release.
This should be fixed in version 13.21.84-1 of anaconda.
In anaconda-13.21.108-1 manual configuration was entered after adding additional repository and eth0 was indeed configured with the specified manual settings.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.