Red Hat Bugzilla – Bug 1249750
Two ifcfg files for one interface when installing with net.ifnames=0
Last modified: 2016-11-29 07:38:03 EST
Description of problem:
There are two ifcfg files for one network device after installation on s390x with the "net.ifnames=0" boot option:
[root@rtt7 ~]# ls /etc/sysconfig/network-scripts/ifcfg-eth0*
The configuration files differ.
Version-Release number of selected component (if applicable):
RHEL-7.1 GA (anaconda-19.31.123-1.el7)
Steps to Reproduce:
1. start the installation with the "net.ifnames=0" boot option
2. proceed through the installation
3. reboot to installed system
Two different config files for one network device:
One ifcfg file per network device
Anaconda creates extra connection because it doesn't recognize ifcfg file created in dracut because it has neither HWADDR (because it is s390) nor DEVICE (because we are using kernel names instead of persistent names, net.ifnames=0) binding info. Assuming dracut's ifcfg file is fine, we probably need to look for NAME in this case.
Here is updates image for RHEL-7.2-20150803.n.0 with a patch:
Does it fix your case?
Thanks for testing, this update should do better (I gave it some checking with fake ifcfg in vm).
v2 works fine. There is just one ifcfg file, as expected.
(In reply to Radek Vykydal from comment #10)
> Thanks for testing, this update should do better (I gave it some checking
> with fake ifcfg in vm).
Retested with anaconda-22.214.171.124-1.el7, this issue is no longer reproducible, there is just one ifcfg file created (ifcfg-eth0) when installing with the net.ifnames=0 boot option.
Thanks, moving to VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.