Comment # 2 on bug 1172381 from Josef Reidinger

(In reply to Michal Filka from comment #1)
> the only difference i can see is that in first case you have (In reply to
> Per Jessen from comment #0)
> > When I install TW on NFS, the system never boots the fist time.  I always
> > have to reboot the installer and rebuild the initrd.  To me it looks like a
> > lack of /etc/resolv.conf when the first initrd is being built. 
> > 
> > Built during installation:
> > root=nfs4:rootserver:/srv/nfsroot/mole28:rw,relatime,vers=4.1,rsize=131072,
> > wsize=131072,namlen=255,hard,proto=tcp6,timeo=600,retrans=2,sec=sys,
> > clientaddr=2a03:7520:4c68:1:ff99:ffff:0:93cd,local_lock=none,addr=2a03:7520:
> > 4c68:1::128
> > ifname=eth0:00:30:48:d3:75:74 ip=eth0:static
> > 
> 
> this "static" looks weird to me. AFAIK ip boot param doesn't know such
> keyword. Moreover the static configuration is not provided at all.
> 
> @Josef:
> are we responsible for creating kernel boot params list in this case?

well, yes. Bootloader copy installation kernel parameters to target system
parameters. But if I get issue, it is about missing resolv.conf in dracut,
maybe issue is that we run dracut in target system and that system maybe
missing resolv.conf which lives in during installation in insts-sys and not
target system?