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, anaconda-14.17.4 How reproducible: Always 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. Expected results: Configuration set in nm-c-e is used Additional info: Attaching tested patch
Proposing as F14 Blocker with hope for Nice To Have. The patch in master: http://git.fedorahosted.org/git/?p=anaconda.git;a=commit;h=2978f4418f0d6c1d0f64cab9056bb5c989f2abc9
(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 line).
We discussed this at the 2010-10-08 blocker review meeting and accepted it as a blocker under the criteria dealing with network installation methods, as there's a scenario where this could prevent network install working.
This should be fixed in anaconda 14.19-1.
Moving to ON_QA (see https://admin.fedoraproject.org/updates/anaconda-14.19-1.fc14)
Verified anaconda 14.19 fixes this issue.
anaconda 14.22 is in stable.