Red Hat Bugzilla – Full Text Bug Listing
|Summary:||Cannot get anaconda to try to get kickstart file from any network interface other than eth0|
|Product:||[Fedora] Fedora||Reporter:||Orion Poplawski <orion>|
|Component:||anaconda||Assignee:||Anaconda Maintenance Team <anaconda-maint-list>|
|Status:||CLOSED NOTABUG||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2007-10-24 15:52:21 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description Orion Poplawski 2007-10-19 18:27:55 EDT
Description of problem: anaconda will always try to use eth0. have been using ksdevice=bootif for a while, but that doesn't work. Neither does ksdevice=eth1. Neither does not specifying a device and selecting eth1 from the menu - it still uses eth0! Doing ks=nfs:saga:/export/data1/ks/rawhide-second.cfg Version-Release number of selected component (if applicable): 22.214.171.124
Comment 1 Chris Lumens 2007-10-22 13:49:22 EDT
Please try again with 126.96.36.199 or later as some work has gone on here recently.
Comment 2 Orion Poplawski 2007-10-23 13:29:05 EDT
Still the same with 188.8.131.52.
Comment 3 Chris Lumens 2007-10-24 15:01:39 EDT
Can you attach your kickstart file and /tmp/anaconda.log to this bug report? Are you booting from the network or from media? How are you determining that eth0 is always the interface being used?
Comment 4 Orion Poplawski 2007-10-24 15:52:21 EDT
Okay, this was my bad. Seems like F7 required a "--device" arg to network? I had ended up doing: network --proto=dhcp --device=eth0 in my kickstart. Removing --device allowed it to work again. Sorry for the false report.