Bug 1362173 - When stop NetworkManager service and start network service, the NetworkManager don't remove the /etc/resolv.conf
Summary: When stop NetworkManager service and start network service, the NetworkManag...
Keywords:
Status: CLOSED DUPLICATE of bug 1367551
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-01 13:05 UTC by Xibo Ning
Modified: 2017-02-08 11:30 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-02-08 11:30:06 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.