Bug 588192

Summary: RA-learned nameservers flaps in and out of /etc/resolv.conf
Product: [Fedora] Fedora Reporter: Tore Anderson <tore>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: dcbw
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: NetworkManager-0.8.1-0.1.git20100510.fc12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-03 13:42:37 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Bug Depends On:    
Bug Blocks: 538499    
Attachments:
Description Flags
/var/log/messages none

Description Tore Anderson 2010-05-03 01:58:05 EDT
Created attachment 410898 [details]
/var/log/messages

(NetworkManager-0.8.0-10.git20100502.fc12.x86_64)

In a network with SLAAC and RDNSS-in-RA (no DHCPv6), the nameserver jumps in and out of /etc/resolv.conf.  My radvd.conf is as follows:

> interface eth0 {
> 	AdvSendAdvert on;
> 	MaxRtrAdvInterval 30;
> 	prefix 2001:16d8:ee47::/64 {
> 		AdvAutonomous on;
> 	};
> 	RDNSS 2001:16d8:ee47::5:1aac {};
> };

I'm attaching a log from activating a wired ethernet on my test host.  2001:16d8:ee47::5:1aac showed up in /etc/resolv.conf immediately following the device activation, but it disappeared at 07:50:01 (leaving only the DHCPv4-learned name server in there).  At 07:50:17 a RA was received, and this caused the IPv6 name-server to be re-added.  This seems to happen constantly - at 07:50:47 it also disappeared and at 07:50:17 it reappeared (following the receipt of a RA).

Tore
Comment 1 Dan Williams 2010-05-03 06:04:24 EDT
Fixed in commit c21416e9565b9a1274ca605e7baeee8ce2f6f94f upstream, thanks for the report.
Comment 2 Fedora Update System 2010-05-03 08:22:02 EDT
NetworkManager-0.8.0-11.git20100503.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/NetworkManager-0.8.0-11.git20100503.fc13
Comment 3 Fedora Update System 2010-05-03 08:26:30 EDT
NetworkManager-0.8.0-11.git20100503.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/NetworkManager-0.8.0-11.git20100503.fc12
Comment 4 Tore Anderson 2010-05-03 13:42:37 EDT
I can confirm it's fixed in git20100503, thanks!

Tore
Comment 5 Fedora Update System 2010-05-04 19:50:39 EDT
NetworkManager-0.8.0-11.git20100503.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 6 Fedora Update System 2010-05-05 05:16:10 EDT
NetworkManager-0.8.0-12.git20100504.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/NetworkManager-0.8.0-12.git20100504.fc13
Comment 7 Fedora Update System 2010-05-05 05:18:52 EDT
NetworkManager-0.8.0-12.git20100504.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/NetworkManager-0.8.0-12.git20100504.fc12
Comment 8 Fedora Update System 2010-05-06 03:02:18 EDT
NetworkManager-0.8.0-12.git20100504.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 9 Fedora Update System 2010-05-11 02:54:55 EDT
NetworkManager-0.8.1-0.1.git20100510.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/NetworkManager-0.8.1-0.1.git20100510.fc12
Comment 10 Fedora Update System 2010-06-10 15:06:33 EDT
NetworkManager-0.8.1-0.1.git20100510.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.