15768 2025-02-20 21:44:24 +0000 systemd recipe edits wrong tmpfile.d file for resolv.conf 2025-04-18 02:22:28 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 5.0.7 x86 x86_64 RESOLVED FIXED Medium normal 5.2 1 trent.piepho trent.piepho meta.mr.watcher meta.watcher mingli.yu randy.macleod --- --- Don't know oldest_to_newest 101193 0 trent.piepho 2025-02-20 21:44:24 +0000 The systemd recipe will use sed to try to edit the tmpfiles.d created symlink from /etc/resolv.conf when using systemd-resolved. However, it tries to edit ${D}${exec_prefix}/lib/tmpfiles.d/etc.conf This is the wrong fine since systemd 250. It should now be systemd-resolve.conf 101240 1 randy.macleod 2025-02-27 15:34:50 +0000 Another interesting suggestion. Can you send a patch to the list? 101548 2 trent.piepho 2025-04-03 01:41:15 +0000 It's more complex to fix this than it might appear at first. If one changes the conf file to edit to be the correct one, then it creates a new problem. The alternatives system is also used to make /etc/resolv.conf a symlink to /etc/resolv-conf.systemd, or elsewhere, depending on the alternative chosen for it. If the tmpfiles.d conf file is fixed, then tmpfiles will make a direct link from: /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf But at the same time, alternatives is configured to manage the same symlink as: /etc/resolv.conf -> /etc/resolv-conf.systemd So they end up fighting each other. Updating systemd via opkg will try to change the link. But that's not even all of it. If volatile-binds is included, it will use a symlink from /etc/tmpfiles.d/etc.conf to /dev/null to disable to processing of the etc.conf file in /usr/lib/tmpfiles.d. The idea being that files in /etc will be a in a read-only rootfs and tmpfiles.d will fail to make them. As pointed out in the initial bug result, since systemd 250 this link is not in the etc.conf file anymore and so is no longer masked by volatile-binds. 101556 3 randy.macleod 2025-04-03 16:05:09 +0000 Adding my co-worker Mingli who may be able to help 'resolv(.conf)" this issue. 101557 4 trent.piepho 2025-04-03 17:53:30 +0000 I have tested that the system one gets now works with Network Manager. This matters, because NetworkManager uses the link target of /etc/resolv.conf to determine the resolve configuration. It doesn't just lstat("/etc/resolv.conf"), but instead follows all the links and if the final file is "/run/systemd/resolve/…" then it detects systemd-resolved mode. And in case it's not clear, what one gets now is a two link chain: /etc/resolv.conf -> /etc/resolv-conf.systemd /etc/resolv-conf.systemd -> ../run/systemd/resolve/{stub-,}resolv.conf The former link from alternatives and the latter link from the systemd install recipe case for systemd-resolved configuration. 101618 5 randy.macleod 2025-04-10 15:04:18 +0000 Apprently works. I not aware of tha commit that changed things... 101639 6 trent.piepho 2025-04-12 20:20:29 +0000 It's in this commit, https://github.com/systemd/systemd/commit/b15f6eae421ad64773c0be934fd372d1ca230adb It's clear it the file the link is in is changing, and the yocto recipe was never updated to edit this file. 101683 7 mingli.yu 2025-04-18 02:22:28 +0000 Fixed by https://git.openembedded.org/openembedded-core/commit/?id=a3020c11c91304b7400bc19f80e44e7d3720281d