Red Hat Bugzilla – Bug 1311548
Kickstart install with static ip configures interface with DHCP AND static IP
Last modified: 2016-02-24 09:23:16 EST
Description of problem:
I have the following lines in a KS file for a 3 NIC VM:
network --bootproto static --device eth0 --ip 192.168.122.13 --netmask 255.255.255.0 --gateway 192.168.122.1 --nameserver 220.127.116.11 --noipv6 --activate
network --bootproto=static --device=eth1 --ip=192.168.10.254 --netmask=255.255.255.0 --noipv6 --activate
network --bootproto=static --device=eth2 --ip=192.168.20.254 --netmask=255.255.255.0 --noipv6 --activate
When the installation finishes, two IPs for the same subnet are assigned to the same interface eth0, and the DHCP client also running for eth0. One of the IPs is the static I specified, and the other one is being set by the DHCP client, which is running on that interface.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a KS install with the provided network options
2. Launch kickstart install with that file
3. Check network configuration of installed machine
This is the (strange) content of /etc/sysconfig/network-scripts/ifcfg-eth0:
The boot protocol is being set to "dhcp", BUT it is being assigned a static IP address too.
On ifcfg-eth1 and ifcfg-eth2 the BOOTPROTO variable is also being ignored from the kickstart "network --bootproto" directive. This is the content of the generated /etc/sysconfig/network-scripts/ifcfg-eth1:
# Generated by parse-kickstart
ifcfg-etth2 is similarly defined, with BOOTPROTO=none.
It seems that the bootproto option is not being honored when configuring the interfaces.
All ifcfg-ethX config files should have the BOOTPROTO=static in them, instead of the wrong ones.
This bug should be fixed in RHEL 7.3.
- move the --hostname option to some of other network commands
- make the network --hostname the first network command
- add nonexisting --device= to the hostname command
*** This bug has been marked as a duplicate of bug 1272274 ***