Description of problem: On systems with multiple network cards it may be necessary to specify which network device kickstart should use for installs. Kickstart supports this with kernel boot parameter 'ksdevice=ethX'. However redhat-config-netboot doesn't. As a workaround you could add this parameter manually to the appropiate pxelinux.cfg, but redhat-confg-netboot will overwrite this on the next update. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. create a PXE install profile with redhat-config-netboot 2. add ksdevice=ethX to pxelinux.cfg/default 3. add or remove an PXE install profile with redhat-config-netboot Actual results: the ksdevice=ethX parameter is gone Expected results: the ksdevice=ethX parameter should still be there Additional info:
Some issues with incorrect removal of manually configured boot arguments were fixed with the latest system-config-netboot-0.1.33* release - see Bug 167762 and Bug 168415. Please try out the latest system-config-netboot-0.1.33-1_EL4 release for RHEL-4, available from: http://people.redhat.com/~jvdias/system-config-netboot/RHEL-4 Are you seeing the 'ksdevice=' setting being removed by the 0.1.33-1 version ? If so, please let me know - this should not be happening with 0.1.33. Perhaps for Network Install boot configurations, we should always set the ksdevice= parameter to the same value as we would set the ETHNERNET= parameter for diskless clients, so that you can choose the interface used for booting with the GUI both for network install and diskless configurations.
As there is now response from reporter, it was working for previous maintainer and the bug is old, I'm closing this bug as NOTABUG.