|Summary:||insertion of static network IP fails on install|
|Product:||Red Hat Enterprise Linux 6||Reporter:||Thomas Zine <tzine3>|
|Component:||anaconda||Assignee:||Radek Vykydal <rvykydal>|
|Status:||CLOSED INSUFFICIENT_DATA||QA Contact:||Release Test Team <release-test-team>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2011-05-31 20:34:56 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Thomas Zine 2010-11-17 21:17:15 UTC
Description of problem: when adding line: ip=10.0.0.100 gateway=10.0.0.1 dns=10.0.0.1 ksdevice=eth0 ks=ftp://10.0.0.10/ks.cfg unable to download kickstart file, no networking ks=ftp://10.0.0.10/ks.cfg without IP information uses DHCP Version-Release number of selected component (if applicable): How reproducible: consistent Steps to Reproduce: 1. append ip information to network boot disk 2. 3. Actual results: no results Expected results: static Ip Additional info:
Comment 1 Chris Lumens 2010-11-17 21:19:02 UTC
Please attach a picture of what you see on tty3 and tty4 to this bug report. Thanks.
Comment 6 Radek Vykydal 2011-05-20 14:00:54 UTC
Sorry for the delay. Are your sure that your routing static configuation (gateway, dns) is correct? If it is, there are some steps that can be done to debug the issue, but they are not quite simple due to very early stage of installation: In the point of dialog with kickstart fail, press Ctrl-Z, dump your network configuration with ifconfig and route command, and attach screenshot. Also /tmp/syslog file would be useful - to gather it at this stage, you can: rm /etc/sysconfig/network-scripts/ifcfg-eth0 ... this will bring down eth0 with failing static configuration echo "DEVICE=eth0\nBOOTPROTO=dhcp\nONBOOT=yes" > /etc/sysconfig/network-scripts/ifcfg-eth0 ... which would bring up eth0 with (as you said working) dhcp configuration ifconfig and route output screenshot would be good for reference here exit ... will take you back to loader UI where you should be able to continue to the point where shell is available on tty2 (Ctrl-Alt-F2), from where you can cp or scp and attach /tmp/anaconda.log and /tmp/syslog.