Description of problem: The systemd RPM postinstall scriptlet destroys the existing /etc/resolv.conf to symlink it to the systemd-resolved stub resolver version. This breaks DNS in two different scenarios for me. 1. Running the Fedora 33 container image in nspawn results in /etc/resolv.conf being copied from the host as usual, but then installing the systemd RPM removes it. Since resolved isn't running, DNS is broken. 2. I usually have DNSStubListener=no in /etc/systemd/resolved.conf (when I remember it exists), so even when I'm running systemd-resolved, the stub listener is not available. Version-Release number of selected component (if applicable): systemd-246.6-3.fc33 How reproducible: Always Steps to Reproduce: 1. Enter the Fedora-Container-Base-33 image with nspawn 2. dnf -y install systemd Actual results: All further attempts at networking fail due to broken DNS. Expected results: I should be able to install the systemd RPM and continue having networking. Additional info: I just need a way to specify that the existing /etc/resolv.conf should not be destroyed.
Can you please add the link to the fix here?
https://src.fedoraproject.org/fork/zbyszek/rpms/systemd/c/cfb4069374bd08f148eaca890b7abe020fe604c9
FEDORA-2020-3616681a70 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-3616681a70
FEDORA-2020-3616681a70 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-3616681a70` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-3616681a70 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-3616681a70 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.