Comment # 8 on bug 1114569 from Jonathan Kang

(In reply to Ivan Skytte J�rgensen from comment #7)
> Just encountered this problem too.
> 
> /etc/resolv.conf was untouched and wickedd/dns-resolver refused to update it:
> 
> Apr 10 13:04:39 redacted systemd[1]: Starting wicked network management
> service daemon...
> Apr 10 13:04:39 redacted systemd[1]: Started wicked network management
> service daemon.
> Apr 10 13:04:40 redacted dns-resolver[3943]: ATTENTION: You have modified
> /etc/resolv.conf. Leaving it untouched...
> Apr 10 13:04:40 redacted dns-resolver[3945]: You can find my version in
> /etc/resolv.conf.netconfig
> Apr 10 13:04:40 redacted wickedd[3846]: route ipv4 0.0.0.0/0 via 172.16.2.1
> dev eth0#2 type unicast table main scope universe protocol dhcp covered by a
> ipv4:dhcp lease
> Apr 10 13:04:40 redacted dns-resolver[4112]: ATTENTION: You have modified
> /etc/resolv.conf. Leaving it untouched...
> 
> 
> 
> I "solved" it by removing /etc/resolv.conf and restarting wickedd. I have
> 10+ identical installations, and this was the only one showing this bug.
> Perhaps the check-if-file-is-modified has a timing-sensitive bug? If it
> shows up again I will take note of the timestamps of the files.
> 
> hyattregencycalgary18:/etc/openvpn # rpm -q -f /usr/sbin/wickedd
> wicked-0.6.53-lp150.2.6.1.x86_64

It's not the exactly the same issue as the one mentioned in this issue, since
you are using wicked.

Do you still remember the content of /etc/resolv.conf when you found this
issue?
Looks like /etc/resolv.conf is modified by something and netconfig refuse to
update it.