Hide Forgot
Description of problem: When buliding a server with a Kickstart file and the RPMs on a different server, the boot.iso only allows NetworkManager to try DHCP to configure the interface. There's no option to manually configure the interface. Version-Release number of selected component (if applicable): 6.1 Beta How reproducible: Try to boot and point to an external Kickstart file source Actual results: NetworkManager tries to configure the interface via DHCP. Expected results: Option to manually configure interface with IP and Network information. Additional info: This is kind of a show stopper for installing 6.1.
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
(In reply to comment #3) > Description of problem: > > When buliding a server with a Kickstart file and the RPMs on a different > server, the boot.iso only allows NetworkManager to try DHCP to configure the > interface. There's no option to manually configure the interface. Hi Leam, To make sure I am understanding the problem properly, are you only seeing the bad behavior when using distinct servers for the kickstart file versus the product repos? (ie kernel parameters something like this: linux ks=http://serverA/ks.cfg repo=http://serverB/path/to/repos Or does your kernel command line/ks.cfg data look differently ...? Best Regards, Brock
Pass 'asknetwork' on the kernel command line.
Interesting...so far that works. However, it also seems to cause an issue if the Kickstart file as a network configuration line. For example, network --device eth0 --bootproto static --ip 192.168.1.250 --netmask 255.255.255.0 --hostname mynewserver Even taking out the --device, --ip, and --netmask stuff it fails. Which means we'll have to manually set the hostname configuration info once the server is built.