[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
This bug was fixed in the package isc-dhcp - 4.4.1-2.3ubuntu3 --- isc-dhcp (4.4.1-2.3ubuntu3) kinetic; urgency=medium * debian/resolved: chown $statedir to systemd-resolve (LP: #1896772) -- Lukas Märdian Thu, 05 May 2022 10:27:34 +0200 ** Changed in: isc-dhcp (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
Thank you very much, Jamie, for your detailed analysis in #15! I've applied the same fix to isc-dhcp https://launchpad.net/ubuntu/+source/isc-dhcp/4.4.1-2.3ubuntu3 We can consider SRUing this to Jammy and Impish, which are affect too. But it doesn't feel too critical, as systemd-resolved usually wins the race vs NetworkManager/dhclient, as you stated: "but with NetworkManager as the netplan renderer, the dhclient script is called later and the dir is created correctly." I'm marking the systemd component as "Invalid", as the fix is needed in other packages. ** No longer affects: systemd (Ubuntu Jammy) ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: isc-dhcp (Ubuntu) Status: Triaged => Fix Committed ** Also affects: ifupdown (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: isc-dhcp (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Impish) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu Impish) ** Changed in: isc-dhcp (Ubuntu Impish) Status: New => Triaged ** Changed in: isc-dhcp (Ubuntu Jammy) Importance: High => Low ** Changed in: isc-dhcp (Ubuntu Impish) Importance: Undecided => Low ** Changed in: ifupdown (Ubuntu Impish) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
** Tags added: fr-2319 ** Also affects: ifupdown (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: isc-dhcp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: ifupdown (Ubuntu Jammy) Status: New => Fix Released ** Changed in: isc-dhcp (Ubuntu Jammy) Status: New => Triaged ** Changed in: isc-dhcp (Ubuntu Jammy) Importance: Undecided => High ** Tags removed: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
** Changed in: isc-dhcp (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
** Changed in: isc-dhcp (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
This bug was fixed in the package ifupdown - 0.8.36+nmu1ubuntu3 --- ifupdown (0.8.36+nmu1ubuntu3) jammy; urgency=medium * debian/if-up.d/resolved: also chown $statedir to systemd-resolve:systemd-resolve (LP: #1896772) -- Jamie Strandboge Sun, 17 Apr 2022 21:21:49 + ** Changed in: ifupdown (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
** Changed in: ifupdown (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
** Also affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Also affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
I grep'd for 'netif' in /etc and noticed: $ sudo grep -r netif /etc /etc/network/if-down.d/resolved:statedir=/run/systemd/resolve/netif /etc/network/if-up.d/resolved:statedir=/run/systemd/resolve/netif /etc/dhcp/dhclient-exit-hooks.d/resolved:statedir=/run/systemd/resolve/netif /etc/network/if-up.d/resolved and /etc/dhcp/dhclient-exit- hooks.d/resolved have code like this: statedir=/run/systemd/resolve/netif mkdir -p $statedir but do not have a corresponding chown of /run/systemd/resolve/netif. There is a chown for `chown systemd-resolve:systemd-resolve "$statedir/$ifindex"` in /etc/network/if-up.d/resolved and /etc/dhcp/dhclient-exit-hooks.d/resolved. This system has been upgraded many, many times (at least since yakkety). dhclient is being used for this interface. ifupdown is installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
I see this on 22.04 after upgrading from 20.04. $ journalctl |grep 'Failed to save link data' Apr 17 15:25:52 hostname systemd-resolved[19095]: Failed to save link data /run/systemd/resolve/netif/3: Permission denied Apr 17 15:25:52 hostname systemd-resolved[19095]: Failed to save link data /run/systemd/resolve/netif/3: Permission denied $ ls -ld /run/systemd/resolve/netif drwxr-xr-x 2 root root 40 Apr 17 14:46 /run/systemd/resolve/netif (note, I had tried to restart systemd-resolved) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
I still have this Failed to save link data /run/systemd/resolve/netif/2: Permission denied problem on 21.10 when getting a dhcp lease. The netif directory: drwxr-xr-x 2 root root 40 nov. 24 2021 /run/systemd/resolve/netif -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
I have the same issue: systemd-resolved: Failed to save link data /run/systemd/resolve/netif/3: Permission denied The netif folder is indeed owned by root. If I change the ownership to systemd-resolved and restart the service, there is no error but as soon as I reboot the system, the ownership is reverted to root and the error is back. Also, I searched the log for other resolved messages and found the error below as well: nm-dispatcher[4641]: /etc/network/if-up.d/resolved: 12: mystatedir: not found -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
When investigating another issue, I found this line in my journal, repeated a few times: nm-dispatcher[3938]: /etc/network/if-up.d/resolved: 12: mystatedir: not found Not sure if that's related, but it seems suspicious at least. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
I've hit exactly the same problem: tree -p -u -d -L 3 /run/systemd/ ... ├── [drwxr-xr-x systemd-resolve] resolve │ └── [drwxr-xr-x root] netif ... The issue happens with wi-fi interface. Could it be somehow related to iwd? I can add workaround to force proper permissions on the folder but I'd rather digg into the root cause. ** Changed in: systemd (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
On Thu, Oct 01, 2020 at 01:41:46PM -, Dan Watkins wrote: > > How did resolve/netif get owned by root? > > I don't believe I've ever touched it before, so I'm not sure. I haven't > rebooted since that last comment, I'll do that at some point today to > check if ownership reverts to root. Ownership is `root` on boot; whatever is responsible for creating this in /run is presumably to blame? > If it does, what debugging can I perform to determine what's doing it? Let me know! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
> How did resolve/netif get owned by root? I don't believe I've ever touched it before, so I'm not sure. I haven't rebooted since that last comment, I'll do that at some point today to check if ownership reverts to root. If it does, what debugging can I perform to determine what's doing it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
How did resolve/netif get owned by root? It's created by systemd- resolved, which should be running as the systemd-resolve user, as that's the User= set in its service file -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
I've just tested: changing the ownership of /run/systemd/resolve/netif to systemd-resolve:systemd-resolve resolves (haha) this issue. The first restart of systemd-resolved after the change did not address it (because the permissions issue means that the state was not persisted); on a network interface reconnect, the state _is_ persisted, so future systemd-resolved restarts do not lose DNS resolution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
On Thu, Sep 24, 2020 at 09:42:28PM -, Balint Reczey wrote: > The latest upload (246.6-1ubuntu1) may have fixed this as well. This happened again just now when I upgraded my system to the new systemd, so I assume not. Here's a log snippet of restarting: Sep 29 09:28:14 surprise systemd[1]: Starting Network Name Resolution... Sep 29 09:28:15 surprise systemd-resolved[31479]: Positive Trust Anchors: Sep 29 09:28:15 surprise systemd-resolved[31479]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Sep 29 09:28:15 surprise systemd-resolved[31479]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test Sep 29 09:28:15 surprise systemd-resolved[31479]: Using system hostname 'surprise'. Sep 29 09:28:15 surprise systemd[1]: Started Network Name Resolution. At this point, I do not have working DNS resolution. If I reconnect my network interface, then I do get it, but I see this line in the log, repeated multiple times: Sep 29 09:28:23 surprise systemd-resolved[31479]: Failed to save link data /run/systemd/resolve/netif/2: Permission denied /run/systemd/resolve is owned by systemd-resolve, but /run/systemd/resolve/netif is owned by root. Could this be related to the issue I'm observing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
The latest upload (246.6-1ubuntu1) may have fixed this as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
I can't reproduce that on an up to date 20.10 laptop with wifi connection only. Could you please add some more details that could help in reproduction? If you downgrade to systemd 246.4-1ubuntu1 do you still observe this bug? . ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
I haven't been able to reproduce in a lxd container or an EC2 instance; I don't have a convenient way of testing a different NetworkManager system, unfortunately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
