Bug 1048755

Summary: anaconda kickstart: dhcp failed: dhclient is already running - exiting.
Product: [Fedora] Fedora Reporter: Gabriel Donnell <Gabriel.Donnell.Fedora>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 20CC: anaconda-maint-list, dracut-maint-list, g.kaviyarasu, harald, jonathan, jpopelka, thozza, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-10 09:00:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
SOS Report
none
SOS Report with kernel rd.debug option. none

Description Gabriel Donnell 2014-01-06 10:05:18 UTC 
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.
Comment 1 Gabriel Donnell 2014-01-06 10:07:20 UTC 
Created attachment 846006 [details]
SOS Report
Comment 2 Jiri Popelka 2014-01-07 15:16:14 UTC 
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.
Comment 3 Harald Hoyer 2014-01-07 16:05:12 UTC 
please add "rd.debug" to the kernel command line and attach rdsosreport.txt again.

Thank you!
Comment 4 Gabriel Donnell 2014-01-09 00:40:59 UTC 
Created attachment 847434 [details]
SOS Report with kernel rd.debug option.
Comment 5 Gabriel Donnell 2014-01-10 09:00:23 UTC 
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
Comment 6 Gabriel Donnell 2014-01-10 16:59:15 UTC 
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