Comment # 10 on bug 1165366 from Thomas Blume

(In reply to Daniel Molkentin from comment #9)
> (In reply to Marius Tomaschewski from comment #8)
> > (In reply to Daniel Molkentin from comment #7)
> > > Wicked maintainers: Does wicked create the ifcfg- files, or just read from
> > > them as legacy source of information? If so, any guidance on how the code
> > > should work to determine a DHCP vs static IP boot?
> > 
> > Wicked never creates any ifcfg files or another kind of interface
> > configuration.
> > This is done by yast2-network or the user.
> 
> Ok, as expected
> 
> > case $BOOTPROTO in
> >   static)
> >      printf 'ip=%s:static ' ${ifname}
> >      ;;
> >   *dhcp*)
> >      printf 'ip=%s:%s ' ${ifname} ${bootproto}
> >      ;;
> >   esac
> > 
> > There is a BOOTPROTO=6to4 artifact which is basically also BOOTPROTO=static.
> 
> I just realized that this is actually caused by a patch from Thomas
> (9cc1b76087c3ff17609a28f2142c2c62cd6cc97b) which is now also part of 050. I
> didn't realize it at the time but we created a circular dependency between
> the nfs and the network-legacy module this way.

Hm, the error:

sed: can't read /etc/sysconfig/network/ifcfg-: No such file or directory

indicates that $ifname is empty.
That should normally get filled via:

ifname=$(ip -o route get to $nfs_address | sed -n 's/.*dev \([^ ]*\).*/\1/p')

Per could you paste the output of the command:

ip -o route get to $YOUR_NSFSSERVERIP | sed -n 's/.*dev \([^ ]*\).*/\1/p'

where $YOUR_NSFSSERVERIP is the ip of your nfsserver?

on your nfsroot machine?