Red Hat Bugzilla – Bug 343551
Cannot get anaconda to try to get kickstart file from any network interface other than eth0
Last modified: 2008-08-02 19:40:35 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!
Version-Release number of selected component (if applicable):
Please try again with 220.127.116.11 or later as some work has gone on here recently.
Still the same with 18.104.22.168.
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?
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.