[Bug 869797] New: There's no "resolv.conf" on boot (using DHCP)
https://bugzilla.novell.com/show_bug.cgi?id=869797 https://bugzilla.novell.com/show_bug.cgi?id=869797#c0 Summary: There's no "resolv.conf" on boot (using DHCP) Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: nrickert@ameritech.net QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 13.2M0, installed from the DVD image on a UEFI box (Lenovo ThinkServer TS140). When I originally booted, there was no network. I switched to NetworkManager, and now have network. However, there is no "/etc/resolv.conf" other than the one that I hastily created with a text editor. There was a message about "wicked" on startup. Since I am using NetworkManager, I don't know what that is about. There is no "/var/log/messages". And "dmesg" does not have anything about "wicked". In short, something is broken about the networking. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=869797 https://bugzilla.novell.com/show_bug.cgi?id=869797#c1 --- Comment #1 from Neil Rickert <nrickert@ameritech.net> 2014-03-23 17:55:06 UTC --- I went into Yast network settings, and switched the network back to "wicked". A side point -- Yast said that NetworkManager was running, and I should switch to "ifup" to change settings. But it is not possible to switch to "ifup", only to "wicked" or NetworkManager. So that's an out-of-date message. After switching to "wicked" I lost network. On reboot, I had a network back, but still no "resolv.conf". It sure looks as if both "wicked" and "NetworkManager" are running. The information that should go in "resolv.conf" is in the lease file in "/var/lib/wicked". So the router is providing the information. It is not getting to the right place. The file in "/var/lib/dhcp" is empty, and dated Mar 17 (probably the date of generation of the install iso). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=869797 https://bugzilla.novell.com/show_bug.cgi?id=869797#c zhang jiajun <jzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |os.gnome.maintainers@gmail. |ovo.novell.com |com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=869797 https://bugzilla.novell.com/show_bug.cgi?id=869797#c2 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |dimstar@opensuse.org InfoProvider| |nrickert@ameritech.net --- Comment #2 from Dominique Leuenberger <dimstar@opensuse.org> 2014-03-24 09:07:25 UTC --- (In reply to comment #0)
When I originally booted, there was no network. I switched to NetworkManager, and now have network. However, there is no "/etc/resolv.conf" other than the one that I hastily created with a text editor.
NM does not touch resolv.conf once you 'intercept'; this is to not destroy your own work. I'd recommend: switch to NM, remove your manual resolv.conf (rm /etc/resolv.conf) and reboot. If the problem is gone, there is clearly nothing wrong with NM and this bug should go to the wicked mainainers (that sounds almost mean). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=869797 https://bugzilla.novell.com/show_bug.cgi?id=869797#c3 Neil Rickert <nrickert@ameritech.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|nrickert@ameritech.net | --- Comment #3 from Neil Rickert <nrickert@ameritech.net> 2014-03-24 12:40:21 UTC ---
NM does not touch resolv.conf once you 'intercept'; this is to not destroy your own work.
At least in earlier releases, it creates "/etc/resolv.conf.something" (not sure what the "something" is. I've been looking for that file, but it does not show up.
I'd recommend: switch to NM, remove your manual resolv.conf (rm /etc/resolv.conf) and reboot.
I've done that. It does not help. As best I can tell, both "NetworkManager" and "wicked" are running, and perhaps interfering with one another. It looks as if Yast is messing up the switchover between the two. If you can tell me how to manually switch, I'll try that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=869797 https://bugzilla.novell.com/show_bug.cgi?id=869797#c4 --- Comment #4 from Luca Beltrame <lbeltrame@kde.org> 2014-03-26 06:33:52 UTC --- It looks to me that netconfig isn't writing back resolv.conf. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=869797 https://bugzilla.novell.com/show_bug.cgi?id=869797#c5 --- Comment #5 from Luca Beltrame <lbeltrame@kde.org> 2014-03-26 06:37:51 UTC --- Issue spotted: by default NETCONFIG_DNS_POLICY in /etc/sysconfig/network/config is set to "" instead of "auto", hence DNS updates are disabled. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=869797 https://bugzilla.novell.com/show_bug.cgi?id=869797#c6 --- Comment #6 from Neil Rickert <nrickert@ameritech.net> 2014-03-26 14:56:08 UTC --- Thanks. I changed that to "auto", deleted my manually created "resolv.conf", rebooted, and all seems fine. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=869797 https://bugzilla.novell.com/show_bug.cgi?id=869797#c7 kevin vandeventer <pilotgi@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pilotgi@gmail.com --- Comment #7 from kevin vandeventer <pilotgi@gmail.com> 2014-08-05 21:12:44 UTC --- I'm using dvd snapshot 20140801 with the latest updates from factory. My NETCONFIG_DNS_POLICY is already set to "auto" without any changes from me. I still have no network connection when using wicked. NetworkManager is working. I do have resolv.conf with a nameserver which I'm assuming came from NetworkManager. Similar to the first comment in bug#889307 only the localhost is configured when I use wicked. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com