Fedora Account System
Red Hat Associate
Red Hat Customer
My systems never have systemd-resolved installed. It runs unbound DNS server instead. After a system upgrade to f40, systemd-resolved was installed, and had mangled /etc/nsswitch.conf and NetworkManager with /etc/resolv.conf I believe this is partially due to for some reason anaconda getting installed, which pulls it in as dependency. Reproducible: Always Steps to Reproduce: 1. install fedora 38 (or 39?) 2. sudo dnf remove systemd-resolved (and cleanup nsswitch.conf and resolve.conf) 3. do a system upgrade to fedora 40 Actual Results: systemd-resolved running and having modified system configs Expected Results: On systemd with no systemd-resolved installed, sys upgrade should not install systemd-resolved.
I should probably mention that since this server is an unbound DNS server for my LAN, this caused my entire LAN DNS to be not working, since systemd-resolved stole port 53 and caused unbound to fail to start
And what makes you think this is an issue in systemd? Packages don't decide themselves to be installed. They are pulled in via dependecies from somewhere. > I believe this is partially due to for some reason anaconda getting > installed, which pulls it in as dependency. Okay, so I'll pass this to anaconda. Maybe the dep. isn't necessary or it could be changed to a weak one.
Anaconda has a hard dependency on systemd-resolved to ensure that DNS resolution works consistently and reliably during the installation process, which is crucial for network-based tasks such as downloading packages or updates from remote repositories. If a user in an existing installed environment removes systemd-resolved as described in step 2 above, anaconda will be also removed because of the dependency. With missing anaconda from the system, I dont see how an system upgrade will pull in anaconda again - which would indeed in turn pull in systemd-resolved. This needs better reproducibility.
> With missing anaconda from the system, I dont see how an system upgrade will > pull in anaconda again - which would indeed in turn pull in systemd-resolved. Yeah. `dnf repoquery` tells me that anaconda is not required by anything else in the distro, so it's unclear why it would be installed during an upgrade. If you upgraded using dnf, please check /var/log/dnf.log*--it might provide more info.
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days