Description of problem: The latest build is creating a "Network error" while configuring network interface during FTP install. Version-Release number of selected component (if applicable): anaconda: 11.1.0.57-1.x86_64 How reproducible: persistent Steps to Reproduce: 1. Prepare an FTP install using kickstart config file (ks.cfg) here a sample content of ks.cfg i.e. vnc --password install url --url ftp://192.168.3.107/mysrc/fed/x86_64/os lang en_US.UTF-8 keyboard us network --device eth0 --bootproto dhcp --hostname mazatlan # PC has multiple NIC cards, forcing to use "eth0" 2. assumed the kickstart file is located at: ftp://192.168.3.107/mysrc/ks/ks.cfg From initial boot prompt type: linux ksdevice=eth0 ks=ftp://192.168.3.107/mysrc/ks/ks.cfg Actual results: Dynamic IP: sending request for IP information for eth0 Network Error: There was an error configuring your network interface. Expected results: installation should proceed without network error Additional info:
Are there any error messages displayed on VT3?
(In reply to comment #1) > Are there any error messages displayed on VT3? VT3 = virtual terminal?? It hasn't even started the vncserver yet, so no VT yet. Looking at the remote syslog output, the install PC was properly given an IP from DHCP server and able to connect. Otherwise it would have failed downloading the kickstart config file locally. NOTE: It did proceed after pressing [Retry] button during the "Network Error: There was an error configuring your network interface" message. Here are the additional messages before install failed again: Running anaconda, the Fedora Core system installer - please wait... install exited abnormally [1/1] sending termination signals...done sending kill signals...done sending kill signals...done disabling swap... umounting filesystems... you may safely reboot your system.
anaconda-11.1.0.57 was built with a libdhcp release that had a problem regarding network configuration. It could put you in a retry loop. That was fixed post 11.1.0.57. The install exited abnormally error you're seeing now is when it goes to launch the stage2 portion of the installer. It has succeeded in getting stage2 via the network, but fails to launch it. The last few builds we've had were missing libraries in the stage2 image. We're fixing that now. Thanks for the report.
This problem has been fixed in the latest rawhide tree.