Bug 1362173

Summary:	When stop NetworkManager service and start network service, the NetworkManager don't remove the /etc/resolv.conf
Product:	[Fedora] Fedora	Reporter:	Xibo Ning <xning>
Component:	NetworkManager	Assignee:	Lubomir Rintel <lkundrak>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	24	CC:	dcbw, fgiudici, lkundrak, psimerda, thaller
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-08 11:30:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Xibo Ning 2016-08-01 13:05:07 UTC

Description of problem:
To create some IP aliases, I stop the NetworkManager service and started the network service. I config my network card dhcp. Then there was not any name server available. I checked the /etc/resolv.conf file, and then I found the file is a soft link pointed to /var/run/NetworkManager/resolv.conf, and no such file.

Version-Release number of selected component (if applicable):
NetworkManager-1.2.2-2.fc24.x86_64

How reproducible:


Steps to Reproduce:
1. service NetworkManager stop
2. service network start
3. ping -c 3 github.com

Actual results:
ping: github.com: Name or service not known

Expected results:
ping works well

Additional info:
After remove the /etc/resolv.conf, restart the network service, the issue is gone.

Comment 1 Thomas Haller 2017-02-08 11:30:06 UTC


*** This bug has been marked as a duplicate of bug 1367551 ***