I have adjusted my isolinux.cfg to ask for network config during my kickstart install.
CODE: SELECT ALL
menu label Install a server
append initrd=initrd.img ks=cdrom:/ks/server1.cfg asknetwork noipv6 biosdevname=0
My kickstart has the following config
CODE: SELECT ALL
network --device=eth0 --onboot=on --hostname=server1
network --device=eth1 --onboot=on --bootproto=static --ip=184.108.40.206 --netmask=255.255.255.252 --nameserver=127.0.0.1
As expected during the text install I am requested to enter static IP data
However at the end of the install my eth0 config is set to dhcp and not the static IP I entered during install.
One clue is I have a static IP set for eth1 in the kickstart which shows as the default IP address for me to adjust when I select static on install. The dialogue box does not indicate which interface I am adjusting.
Is this a known issue?
Please attach /tmp/*log (including /tmp/syslog) anaconda logs and the kickstart file. You can use scp or copy to local storage in shell in tty2 (Ctlr-Alt-F2) during installation.
You can also find the log files on installed system:
I'm just putting together the log files but the one thing I found was if I opted for DHCP all worked well but if I opted to enter static IP configuration during install it failed. After a few tests I found that the config for eth0 always had DHCP set for BOOTPROTO.
It looks like this is not set correctly if you use the asknetwork option appended to your isolinux.cfg boot command.
I'm getting round this by running a post install script to change the BOOTPROTO to static but it means I can't opt for DHCP if I wanted to.
Is the issue related to this bug report?
Created attachment 1005095 [details]
Created attachment 1005096 [details]
Created attachment 1005097 [details]
Created attachment 1005098 [details]
Created attachment 1005099 [details]
kick start file
Created attachment 1005100 [details]
Created attachment 1005101 [details]
Created attachment 1005102 [details]
Created attachment 1005103 [details]
Created attachment 1005104 [details]
If I set a second interface eth1 for example, The settings from the dialog box during install comes through as eth0 and the two sets of interface configurations are mixed.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: