Bug 473785
| Summary: | NetworkManager generates useless /etc/resolv.conf | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joachim Backes <joachim.backes> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 10 | CC: | arxs, dcbw, wtogami, yrtimid, ywb_bsd |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-10-15 04:06:57 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Joachim Backes
2008-11-30 15:50:01 UTC
I confirm this bug. Have same behavior. versions: NetworkManager-0.7.0-0.12.svn4326.fc10.i386 dhcp-4.0.0-33.fc10.i386 dhclient-4.0.0-33.fc10.i386 output of /var/log/messages after "service NetworkManager start": Dec 11 22:23:18 localhost NetworkManager: <info> starting... Dec 11 22:23:18 localhost NetworkManager: <WARN> nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add():#012Sucess#012 Dec 11 22:23:18 localhost NetworkManager: <info> eth1: driver is '8139too'. Dec 11 22:23:18 localhost NetworkManager: <info> Found new Ethernet device 'eth1'. Dec 11 22:23:18 localhost NetworkManager: <info> (eth1): exported as /org/freedesktop/Hal/devices/net_00_00_21_f3_2a_b7 Dec 11 22:23:18 localhost NetworkManager: <info> eth0: driver is '8139too'. Dec 11 22:23:18 localhost NetworkManager: <info> Found new Ethernet device 'eth0'. Dec 11 22:23:18 localhost NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_00_21_f3_2a_b4 Dec 11 22:23:22 localhost NetworkManager: <info> (eth1): device state change: 1 -> 2 Dec 11 22:23:22 localhost NetworkManager: <info> (eth1): bringing up device. Dec 11 22:23:22 localhost kernel: eth1: link up, 100Mbps, full-duplex, lpa 0xC5E1 Dec 11 22:23:22 localhost NetworkManager: <info> (eth1): preparing device. Dec 11 22:23:22 localhost NetworkManager: <info> (eth1): deactivating device (reason: 2). Dec 11 22:23:22 localhost NetworkManager: <info> (eth1): carrier now ON (device state 2) Dec 11 22:23:22 localhost NetworkManager: <info> (eth1): device state change: 2 -> 3 Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth1) starting connection 'System eth1' Dec 11 22:23:22 localhost NetworkManager: <info> (eth1): device state change: 3 -> 4 Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Dec 11 22:23:22 localhost NetworkManager: <info> (eth0): device state change: 1 -> 2 Dec 11 22:23:22 localhost NetworkManager: <info> (eth0): bringing up device. Dec 11 22:23:22 localhost kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Dec 11 22:23:22 localhost NetworkManager: <info> (eth0): preparing device. Dec 11 22:23:22 localhost NetworkManager: <info> (eth0): deactivating device (reason: 2). Dec 11 22:23:22 localhost NetworkManager: <info> (eth0): carrier now ON (device state 2) Dec 11 22:23:22 localhost NetworkManager: <info> (eth0): device state change: 2 -> 3 Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started... Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete. Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth0) starting connection 'System eth0' Dec 11 22:23:22 localhost NetworkManager: <info> (eth0): device state change: 3 -> 4 Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting... Dec 11 22:23:22 localhost NetworkManager: <info> (eth1): device state change: 4 -> 5 Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) successful. Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled. Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete. Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started... Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started... Dec 11 22:23:22 localhost NetworkManager: <info> (eth1): device state change: 5 -> 7 Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) scheduled... Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete. Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting... Dec 11 22:23:22 localhost NetworkManager: <info> (eth0): device state change: 4 -> 5 Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) started... Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled... Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) complete. Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... Dec 11 22:23:22 localhost NetworkManager: <info> (eth0): device state change: 5 -> 7 Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth0) Beginning DHCP transaction. Dec 11 22:23:22 localhost dhclient: Internet Systems Consortium DHCP Client 4.0.0 Dec 11 22:23:22 localhost NetworkManager: <info> dhclient started with pid 12296 Dec 11 22:23:22 localhost dhclient: Copyright 2004-2007 Internet Systems Consortium. Dec 11 22:23:22 localhost dhclient: All rights reserved. Dec 11 22:23:22 localhost dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Dec 11 22:23:22 localhost dhclient: Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Dec 11 22:23:22 localhost NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started... Dec 11 22:23:22 localhost dhclient: Listening on LPF/eth0/00:00:21:f3:2a:b4 Dec 11 22:23:22 localhost dhclient: Sending on LPF/eth0/00:00:21:f3:2a:b4 Dec 11 22:23:22 localhost dhclient: Sending on Socket/fallback Dec 11 22:23:23 localhost NetworkManager: <info> (eth1): device state change: 7 -> 8 Dec 11 22:23:23 localhost NetworkManager: <info> Policy set 'System eth1' (eth1) as default for routing and DNS. Dec 11 22:23:23 localhost NetworkManager: <info> Activation (eth1) successful, device activated. Dec 11 22:23:23 localhost NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete. Dec 11 22:23:23 localhost NetworkManager: <info> DHCP: device eth0 state changed (null) -> preinit Dec 11 22:23:24 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 Dec 11 22:23:24 localhost dhclient: DHCPOFFER from 10.163.128.1 Dec 11 22:23:24 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Dec 11 22:23:24 localhost dhclient: DHCPACK from 10.163.128.1 Dec 11 22:23:24 localhost dhclient: bound to 84.XXX.XXX.190 -- renewal in 34583 seconds. Dec 11 22:23:24 localhost NetworkManager: <info> DHCP: device eth0 state changed preinit -> bound Dec 11 22:23:24 localhost NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... Dec 11 22:23:24 localhost NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) started... Dec 11 22:23:24 localhost NetworkManager: <info> address 84.XXX.XXX.190 Dec 11 22:23:24 localhost NetworkManager: <info> prefix 22 (255.255.252.0) Dec 11 22:23:24 localhost NetworkManager: <info> gateway 84.XXX.XXX.1 Dec 11 22:23:24 localhost NetworkManager: <info> hostname 'yserver' Dec 11 22:23:24 localhost NetworkManager: <info> nameserver '192.117.235.235' Dec 11 22:23:24 localhost NetworkManager: <info> nameserver '62.219.186.7' Dec 11 22:23:24 localhost NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... Dec 11 22:23:24 localhost NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) complete. Dec 11 22:23:24 localhost NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... Dec 11 22:23:25 localhost NetworkManager: <info> Policy set 'System eth1' (eth1) as default for routing and DNS. Dec 11 22:23:25 localhost NetworkManager: <info> (eth0): device state change: 7 -> 8 Dec 11 22:23:25 localhost NetworkManager: <info> Activation (eth0) successful, device activated. Dec 11 22:23:25 localhost NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. resolv.conf after "start" finished: # No nameservers found; try putting DNS servers into your # ifcfg files in /etc/sysconfig/network-scripts like so: # # DNS1=xxx.xxx.xxx.xxx # DNS2=xxx.xxx.xxx.xxx # DOMAIN=lab.foo.com bar.foo.com I also have problem with NetworkManager to create a usable /etc/resolv.conf when /etc/sysconf/readonly-root is modified with TEMPORARY_STATE="yes". The problem seems to be NetworkManager attempt to create a temporary file called /etc/resolv.conf.tmp first then copies it back to the bind-mounted /etc/resolv.conf which is causing a device busy kind of error. I haven't looked into the source code of NetworkManager but I have similar problems with /etc/mtab under fuse/zfs-fuse which is also trying to mv /etc/mtab.tmp to /etc/mtab which is also bind-mounted to the /var/lib/stateless/writable/etc/mtab. When I unmount zfs filesystems, it will emit error messages telling me unable to rename /etc/mtab.tmp to /etc/mtab because the device is busy. I think change the mv to cat with a redirection to the bind-mounted file will solve these problems. The problem in my box seems to be another one: cat /etc/sysconfig/readonly-root ----------------------------- snip ---------------------- # Set to 'yes' to mount the system filesystems read-only. READONLY=no # Set to 'yes' to mount various temporary state as either tmpfs # or on the block device labelled RW_LABEL. Implied by READONLY TEMPORARY_STATE=no # Place to put a tmpfs for temporary scratch writable space RW_MOUNT=/var/lib/stateless/writable # Label on local filesystem which can be used for temporary scratch space RW_LABEL=stateless-rw # Options to use for temporary mount RW_OPTIONS= # Label for partition with persistent data STATE_LABEL=stateless-state # Where to mount to the persistent data STATE_MOUNT=/var/lib/stateless/state # Options to use for peristent mount STATE_OPTIONS= ---------------------- snap ------------------------------ Then, do I need to file another bug report? (In reply to comment #3) > The problem in my box seems to be another one: > > cat /etc/sysconfig/readonly-root > ----------------------------- snip ---------------------- > # Set to 'yes' to mount the system filesystems read-only. > READONLY=no > # Set to 'yes' to mount various temporary state as either tmpfs > # or on the block device labelled RW_LABEL. Implied by READONLY > TEMPORARY_STATE=no > # Place to put a tmpfs for temporary scratch writable space > RW_MOUNT=/var/lib/stateless/writable > # Label on local filesystem which can be used for temporary scratch space > RW_LABEL=stateless-rw > # Options to use for temporary mount > RW_OPTIONS= > # Label for partition with persistent data > STATE_LABEL=stateless-state > # Where to mount to the persistent data > STATE_MOUNT=/var/lib/stateless/state > # Options to use for peristent mount > STATE_OPTIONS= > ---------------------- snap ------------------------------ Is /etc/ mounted as a tmpfs or something like that? Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers 1. No, /etc/ is not mounted as tmpfs or something other. 2. Since some NetworkManager versions, my /etc/resolv.conf is OK (I reported this already to another thread). Ok, thanks for the report. Please let us know if this happens again! |