Thomas Blume changed bug 1003872
What Removed Added
CC   mt@suse.com
Flags   needinfo?(mt@suse.com)

Comment # 11 on bug 1003872 from
(In reply to Thomas Blume from comment #10)
> So, it is correct when looking at it from the nfs server.
> Question is where it pointed to in the installer.

I can reproduce the issue in the installed system. Due to missing nfsserver
entries in resolv.conf, dracut doesn't find the device setup for the nic that
provides the nfs mount. Hence it defaults to static instead of the ifcfg
BOOTPROTO setting:

-->
+++ head -n1
+++ host nfsserver
++ lookup=
++ nfs_address=
+++ sed -n 's/.*dev \([^ ]*\).*/\1/p'
+++ ip -o route get to
Command line is not complete. Try option "help"
++ ifname=
++ '[' -d /sys/class/net//bonding ']'
++ '[' -e /sys/class/net//address ']'
+++ sed -n '/BOOTPROTO/s/BOOTPROTO='\''\([[:alpha:]]*6\?\)4\?'\''/\1/p'
/etc/sysconfig/network/ifcfg-
sed: can't read /etc/sysconfig/network/ifcfg-: No such file or directory
++ bootproto=
++ '[' ']'
++ printf 'ip=%s:static '
--<

The netconfig provided resolv.conf is empty:

-->
kvm112:~ # cat /var/run/netconfig/resolv.conf
### /etc/resolv.conf is a symlink to /var/run/netconfig/resolv.conf
### autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
#     NETCONFIG_DNS_STATIC_SEARCHLIST
#     NETCONFIG_DNS_STATIC_SERVERS
#     NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
### Call "netconfig update -f" to force adjusting of /etc/resolv.conf.
kvm112:~ # 
--<

even though the wicked lease shows an dns server entry:

-->
kvm112:~ # cat /var/lib/wicked/lease-eth0-dhcp-ipv4.xml
<lease>
[...]
    <dns>
      <domain>virt.net</domain>
      <server>192.168.57.1</server>
      <search>virt.net</search>
    </dns>
  </ipv4:dhcp>
</lease>
--<

Marius, apparently netconfig doesn't take the dhcp provided nameserver.
Could you take a look?


You are receiving this mail because: