Comment # 17 on bug 1003872 from Marius Tomaschewski

Ah... seems I didn't understood the scenario/comments correctly before.

Please correct me when I still didn't:

The installer is using wicked to setup network in the installer root-fs,
what works fine: wicked is passing the nameservers,... to netconfig and
netconfig puts it to /etc/resolv.conf -> /var/run/netconfig/resolv.conf.
The installer is able to access the source repositories, mount the nfs
root and installs the packages to the nfs root (mounted in /mnt AFAIR).

Then it chroots to the nfsroot and calls dracut / mkinitrd, which can't
find anything about the network configuration nor resolve nameservers
and assumes "ip=:static" setup with missing interface name + no info
about dhcp.

Perhaps, the installer is copying the /etc/resolv.conf link, but not
the file it points to, but maybe not even this, because it happens on
Leap-42.2b3 ��� Leap-15.0 where /etc/resolv.conf was still a file - the
resolv.conf link has been added on Leap-15.1 and SLES-15-SP1 via:

- version 0.85.0
- netconfig: change to write resolv.conf,yp.conf,forwarders.conf
  to files in /[var/]run/netconfig/ and link in /etc (fate#325872)

Thus this is clearly not a wicked nor netconfig issue, but an old
installer issue, which does not prepare the nfs root sufficiently
before it calls dracut / mkinitrd inside it.

Also, changing to Leap-15.1 as Thomas confirmed it in comment 9.

-> Therefore I reassign it to yast2 / installer maintainers.