Hide Forgot
Description of problem: DEVICE property set in KS file is not written in ifcfg-<DEVICE>. All information passed in kickstart file with field "network" are applied in the related ifcfg-<DEVICE>, except for DEVICE. This cause ifupcfg init script to fails looking for target DEVICE for passed configuration. Version-Release number of selected component (if applicable): 21.48.22.56-1 How reproducible: Run dracut with options net.ifnames=0 biosdevname=0 ksdevice=bootif Steps to Reproduce: 1. pxe installation of rhel 7.2 using ks file from http and inst.repo from nfs 2. ks file are two: default + custom (network and disk layout) 3. NetworkManager is disabled and network enable in ks file 4. run dracut with options net.ifnames=0 biosdevname=0 ksdevice=bootif Actual results: Anaconda seems to find an eth0 net card but in file ifcfg-eth0 all properties are written except for DEVICE=etho, this mean that during network service bootstrap ifupcfg is not able to pair interface. Expected results: DEVICE=eth0 should be present when NetworkManager is disabled (I guess). Additional info: I've applied a work around adding DEVICE=eth0 in the %%post kickstart phase and configuration is perfectly applied on first reboot.
Please attach installation logs as separate text/plain attachments. They can be gathered (eg using scp) from shell in tty2 in installation environment from /tmp or from installed system from /var/log/anaconda. We need these log files: anaconda.log ifcfg.log syslog program.log Also it would be helpful to try to reproduce with RHEL 7.3 release when available.
Created attachment 1216968 [details] anaconda.log
Created attachment 1216969 [details] storage.log
Created attachment 1216983 [details] syslog
Created attachment 1216984 [details] ifcfg.log
Created attachment 1216985 [details] program.log
Dracut is not writing DEVICE value in ifcfg file in case kernel network device naming is used (net.ifnames=0 biosdevname=0) which makes sense as in this case the device names are not assigned predictably (can change across reboots) so the configuration is bound to MAC address. I think network service should be able to cope with such ifcfg file though and in my tests it does so. Could you please attach the error messages you are getting when the service is unable to pair the interface? Are we talking about network service here or some other service (ifupcfg?). Are you installing and booting on the same system (ie the MAC address of the NIC the same)? Also it could be helpful to attach also kickstart (at least network configuration) you are using.
This setup should use "net.ifnames=0 biosdevname=0" to obtain ethX naming on installation and boot. This cause all customer customizations are based on old nic naming. It's that approach still correct? I'll attach ifupcfg error asap. Consider that we're using a post-installation command to add device=ethx to ifcfg-XXX file and works perfectly.
You can attach the installation logs as separate text/plain attachments. http://www.followthesteps.net/hsbc-contact-phone-number/
Adding DEVICE=eth0 in the post kickstart phase and configuration is perfectly applied on first reboot. http://www.fixithere.net/sky-customer-service/
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.