Bug 1472997 - broken /etc/resolv.conf -> /var/run/connman/resolv.con @boot
broken /etc/resolv.conf -> /var/run/connman/resolv.con @boot
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
26
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Lubomir Rintel
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-19 15:36 EDT by lejeczek
Modified: 2017-08-07 12:23 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-07 11:32:50 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description lejeczek 2017-07-19 15:36:52 EDT
Description of problem:

I have to remove /etc/resolv.conf and reconnect to wifi network and then I see no softlink and all is good.

Version-Release number of selected component (if applicable):

NetworkManager-1.8.0-6.fc26.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 lejeczek 2017-08-07 06:29:09 EDT
hi guys, any chance somebody could look into it?
It happens every time system reboot.

$rm -f /etc/resolv.conf

reconnect to PA, reboot fedora and again.
Comment 2 Francesco Giudici 2017-08-07 08:05:45 EDT
Hi lejeczek,
   not sure to understand your issue correctly...
Is the issue that at every boot you have /etc/resolv.conf as a symlink to  /var/run/connman/resolv.con ?

If so, NetworkManager will not touch /etc/resolv.conf at all (a symlink means to NetworkManager that resolv.conf is managed by another package).
That's the expected behavior, no bug here on NM.
You probably want (connman?) to avoid creating that simlynk.

For NetworkManager, you can see the available options for resolv.conf management in NetworkManager.conf man page: look at "dns" and "rc-manager" keys.
Comment 3 lejeczek 2017-08-07 09:27:18 EDT
Surprising is that nobody else sees it?
I have had working nm, no problems and an upgrade from f25 to f26 did it, until then I did not even hear about connman. I don't really know that connman at all.
Comment 4 Francesco Giudici 2017-08-07 11:32:50 EDT
(In reply to lejeczek from comment #3)
> Surprising is that nobody else sees it?
> I have had working nm, no problems and an upgrade from f25 to f26 did it,
> until then I did not even hear about connman. I don't really know that
> connman at all.

connman is a network management daemon. If you use NM, you don't need it.
It is not installed by default on fedora.. probably you add it some time ago and in the last fedora update it has been updated to the newer version, including this simlynk behavior.

I tried to install it on a fresh f26 VM and here we are: the simlynk appeared as you described.

Just remove connman and delete for the last time the simlynk:
dnf remove connman; rm /etc/resolv.conf

Closing the bug, reopen if needed.
Comment 5 lejeczek 2017-08-07 11:35:28 EDT
nope, no connman on my installation, never was, like I said, never heard of it.

$ rpm -qa \*connman\*
$
Comment 6 Francesco Giudici 2017-08-07 12:23:39 EDT
(In reply to lejeczek from comment #5)
> nope, no connman on my installation, never was, like I said, never heard of
> it.
> 
> $ rpm -qa \*connman\*
> $

Well, that's weird.
Anyway, the file responsible for the simlynk creation at boot was a systemd-tmpfile:
/usr/lib/tmpfiles.d/connman_resolvconf.conf

Check on your system, you will probably have that file. If not check also in:
/etc/tmpfiles.d/
/run/tmpfiles.d/

Then, before deleting the file, would be interesting to see if it comes from any package (rpm -qf)

Note You need to log in before you can comment on or make changes to this bug.