Why does anaconda not honoring --nodefroute option in kickstart installation of Red Hat Enterprise Linux 6.6?
Issue
- While configuring 2 different interfaces in a kickstart with one configured as
onboot=no, it's gateway is still set in/etc/sysconfig/networkthus causing a failure to have network connectivity post-install. - Here is the relevant portion of our kickstart file:
network --activate --hostname=testserver --device bond0 --ip=192.168.100.200 --gateway=192.168.100.254 --netmask=255.255.255.0 --nameserver=192.168.100.1 --onboot=no --noipv6 --bondslaves=eth0,eth1 --bondopts=mode=active-backup,miimon=100,use_carrier=1 --bootproto=static
network --activate --device eth2 --onboot=yes --noipv6 --bootproto=dhcp --hostname testserver
- After installation, the interface
eth2is up and has an IP plus it received the routers option in the DHCP lease too. So no problem with that. - However the
gatewayforbond0(which is set asonboot=no) has been configured in/etc/sysconfig/networkand that is to overriding any other gateway for other interfaces until theGATEWAY=line is commented out and the network service is restarted as seen here:
# cat /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=testserver
#GATEWAY=192.168.100.254
NM_BOND_VLAN_ENABLED=yes
- Even after use of
--nodefrouteoption forbond0configuration, it's not working as expected.
network --activate --nodefroute --hostname=testserver --device bond0 --ip=192.168.100.200 --gateway=192.168.100.254 --netmask=255.255.255.0 --nameserver=192.168.100.1 --onboot=no --noipv6 --bondslaves=eth0,eth1 --bondopts=mode=active-backup,miimon=100,use_carrier=1 --bootproto=static
network --activate --device eth2 --onboot=yes --noipv6 --bootproto=dhcp --hostname testserver
Environment
- Red Hat Enterprise Linux 6.6
- Kickstart installation
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
