Hide Forgot
Description of problem: Twice (out of many years updating every week) the upgrade has replaced my real file /etc/resolv.conf with the original symbolic link. This is a disaster to browser access of the net. Version-Release number of selected component (if applicable): n.a. How reproducible: When it happens 100%. Steps to Reproduce: 1. dnf upgrade 2. 3. Actual results: When it happens, network access to any named web site is stopped with "server not found". Expected results: When a user has replaced the symbolic link (as instructed to in the symbolic link file pointing to /run/systemd/resolve/resolv.conf), /etc/resolv.conf should not be changed during an upgrade - certainly NOT relinked to the original link. Additional info: Perhaps the fault is NOT with dnf itself, but with the instructions given it by the upgrade request. I do not know how to direct this bug to the attention of the group doing that.
As you mentioned, dnf is definitely not changing the symlink. It has to be done by some rpm package that was part of the upgrade. I guess the culprit is systemd-resolved which creates the symlink in its scriptlets, so I re-assign it there for further investigation.
Yeah, the rpm scriptlet had a check for whether we're doing an upgrade or initial installation, but that check was borked.
OK, please don't bork it again. :=]]] Sorry, but I just plain forgot about it and spent 2 hours thinking it was hardware. My boof!
FEDORA-2022-01079468a3 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-01079468a3
FEDORA-2022-01079468a3 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-01079468a3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-01079468a3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Thanks to all of you. Nice.
5/7/2022 and I just did a system upgrade. I had a real file in /etc/resolv.conf (I copy in mine and do not use a symlink anymore) AND I have a file called /etc/NetworkManager/conf.d/no-dns.conf contining these 2 lines [main] dns=none ALL TO NO AVAIL. The upgrade replaced my real file with the symlink to the generated file. BOO HOO HOO. At least I remembered this time, so the fix only took a minute.
FEDORA-2022-01079468a3 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.