Bug 1363831 - No nameserver in /etc/resolv.conf after iSCSI installation with static IP address
Summary: No nameserver in /etc/resolv.conf after iSCSI installation with static IP add...
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.3
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
Milan Navratil
Depends On:
Blocks: 1256306
TreeView+ depends on / blocked
Reported: 2016-08-03 16:47 UTC by Jan Stodola
Modified: 2020-12-15 07:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
No name server is included in `/etc/resolv.conf` after an iSCSI installation with a static IP address When connecting to the root file system on an iSCSI target from an interface with a static IP address, the name server is not configured on the installed system. To work around this problem, add the "nameserver=<IP>" kernel option to the boot loader configuration of the installed system.
Clone Of:
Last Closed: 2020-12-15 07:44:02 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Jan Stodola 2016-08-03 16:47:08 UTC
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
[root@localhost ~]#

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):
RHEL-7.3-Alpha (anaconda-

How reproducible:

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

kickstart snippet:

iscsiname iqn-2012-12.com.redhat:76765
iscsi --ipaddr= --target=iqn.2009-02.com.example:for.all
bootloader --location=mbr
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

Actual results:
no nameserver in /etc/resolv.conf

Expected results:
nameserver(s) present in /etc/resolv.conf

Comment 5 RHEL Program Management 2020-12-15 07:44:02 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.