Description of problem: Fedora 20 anaconda kickstart encounters dhcp failure which does not occur on Fedora 19 with the same Kickstart Framework (DHCP Server, NFS Storage, Kickstart File, etc). Please refer to the SOS Report (rdsosreport.txt) File that is attached. Version-Release number of selected component (if applicable): Fedora 20 anaconda & dhcp How reproducible: Everytime Steps to Reproduce: 1. Network Installation with PXE Boot. 2. Select Fedora 20 Media. 3. Observe Load & DHCP Failure Message. Actual results: Long wait before DHCP Failure Message. Expected results: Fedora 20 Installation. Additional info: Fedora 19 with the same Kickstart Framework (DHCP Server, NFS Storage, Kickstart File, etc). Please refer to the SOS Report (rdsosreport.txt) File that is attached.
Created attachment 846006 [details] SOS Report
Something seems to run more dhclient instances for the same interface. Not sure it's anaconda, dracut or NM but looks like dracut so let's pass it there.
please add "rd.debug" to the kernel command line and attach rdsosreport.txt again. Thank you!
Created attachment 847434 [details] SOS Report with kernel rd.debug option.
I resolved the problem by removing the Kickstart Device Specification or changing it as indicated in the following as required only in Fedora 20 because it worked for the previous Fedora Releases. * From: ksdevice=eth0 * To: ksdevice=p2p1 I decided to try the above after referring to the following to determine how I could assign a Static IP Address as a work around to the DHCP Failure. * https://bugzilla.redhat.com/show_bug.cgi?id=836039 * http://fedoraproject.org/wiki/Anaconda/Kickstart * https://fedoraproject.org/wiki/Dracut/Options#Network
The following are also useful references for me. * https://google.com/webhp?source=search_app#q=%22Fedora+20%22+Kickstart+p2p1+eth0 * http://fedoraforum.org/forum/showthread.php?p=1649237 * https://fedoraproject.org/wiki/Features/SystemdPredictableNetworkInterfaceNames