Description of problem:
After kickstart installation with root file system on iSCSI target and using static IP configuration during the installation, /etc/resolv.conf on installed system doesn't contain any nameserver= option:
[root@localhost ~]# cat /etc/resolv.conf
# Generated by NetworkManager
Nameserver was set during the installation using the nameserver= boot option.
The problem is that /etc/sysconfig/network-scripts/ifcfg-eth0 is replaced during boot by ifcfg-eth0 generated by dracut initrd. It's caused by rhel-import-state.service and it's considered as an expected behavior (see bug 1163829).
Since nameserver= is not present on the kernel command line when booting installed system, dracut's ifcfg-eth0 doesn't contain DNSX=<IP> option, which results in no nameserver set on running system.
There is a workaround to manually add "nameserver=<IP>" on the kernel command line when booting the system.
A possible solution is to let anaconda add the nameserver= boot option(s) if static IP configuration is used by dracut to mount a network storage device.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. prepare an iSCSI target
2. run kickstart installation with rootfs on iSCSI, use static IP configuration on the kernel command line
iscsi --ipaddr=192.168.122.27 --target=iqn.2009-02.com.example:for.all
clearpart --all --initlabel
part /boot --asprimary --size=500
part swap --fstype=swap --recommended
part / --grow --size=2048 --ondisk=/dev/disk/by-id/scsi-1IET_00010001
3. check /etc/resolv.conf on installed system
no nameserver in /etc/resolv.conf
nameserver(s) present in /etc/resolv.conf
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.