Description of problem: When performing PXE install through the second (2nd) interface (eth1) instead of (eth0), the install fails because it always probed for DHCP and download kickstart from the first interface (eth0) regardless of whether the kernel command line and/or kickstart file specified the 2nd interface(eth1). Version-Release number of selected component (if applicable): anaconda-runtime-11.4.0.58-1.x86_64.rpm anaconda-11.4.0.58-1.x86_64.rpm How reproducible: persistent Steps to Reproduce: 1. Use two interface cards and PXE install through the 2nd interface (eth1) assigned by the boot program. This is important, install will NOT fail if installed through the first interface eth0 (the algorithm always search for DHCP starting from eth0 then eth1... etc. 2. Here is an example for KERNEL COMMAND LINE (located in pxelinux.cfg/default): kernel /fed/dev/x86_64/os/isolinux/vmlinuz append initrd=/fed/dev/x86_64/os/isolinux/initrd.img ksdevice=eth1 \ ks=http://192.168.3.102/a/ks/f4d3 And the KICKSTAET file (/a/ks/f4d3) url --url http://192.168.3.102/a/fed/dev/x86_64/os network --device eth1 --bootproto dhcp --hostname fiji3 3. Actual results: The program stopped and failed when obtaining IP from DHCP through eth0 instead of eth1 Expected results: The program would continue if it is able to obtain an IP from DHCP through eth1. Additional info:
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
*** This bug has been marked as a duplicate of 447813 ***