This bug was fixed in the package systemd - 237-3ubuntu10.52
---------------
systemd (237-3ubuntu10.52) bionic; urgency=medium
* d/extra/dhclient-enter-resolved-hook:
Reset start limit counter for systemd-resolved in dhclient hook
(LP: #1939255)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ea6710476dde78e8595274c3c4ba7acca6d5162c
* d/p/lp1934147/0001-core-add-a-new-unit-method-catchup.patch,
d/p/lp1934147/0002-cgroup-do-catchup-for-unit-cgroup-inotify-watch-file.patch,
d/p/lp1934147/0003-core-Make-sure-cgroup_oom_queue-is-flushed-on-manage.patch:
Catch up on cgroup empty inotify after reexec/reload (LP: #1934147)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5ef61bd930612a90ce3ed9105cbadc5ff97b6ffc
* d/p/lp1934981-correct-suspend-then-sleep-string.patch:
Fix sleep verb used by logind during suspend-then-hibernate
(LP: #1934981)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1ade873a41ad018a5e07f10775738c6eb8c82310
* d/extra/dhclient-enter-resolved-hook:
Check is-enabled systemd-resolved in dhclient hook (LP: #1853164)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=774c2f82a39a88fa0fd8b2adbfa0b8a8c3cd1fb5
-- Dan Streetman <ddstr...@canonical.com> Thu, 26 Aug 2021 10:20:40
-0400
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: systemd (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1939255
Title:
dhclient triggers systemd-resolved start limit when processing more
than 5 interfaces at once
Status in systemd package in Ubuntu:
Invalid
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
on a system where systemd-resolved is running, if dhclient is used on
more than 5 interfaces, it calls the '/etc/dhcp/dhclient-enter-
hooks.d/resolved' script multiple times, which then restarts systemd-
resolved multiple times, triggering the unit's start-limit throttle
which results in the unit entering failed state
[test case]
on a system with more than 5 available interfaces to run dhclient on
(where all the interfaces will get a dhcp response), run dhclient with
the interfaces:
$ dhclient ens8 ens9 ens10 ens11 ens12 ens13 ens14 ens15
check if systemd-resolved failed:
$ journalctl -b -1 -u systemd-resolved
...
Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Start
request repeated too quickly.
Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Failed with
result 'start-limit-hit'.
Aug 09 00:38:08 sf316232-b systemd[1]: Failed to start Network Name
Resolution.
[regression potential]
failure to start/stop/restart systemd-resolved, or problems adding
dhclient-provided DNS nameservers to systemd-resolved
[scope]
this is needed only for b/f
the dhclient 'hook' script is provided by the systemd package in focal
and earlier, and needs fixing in those releases
in h and later, the 'hook' script is included in the isc-dhcp-client
package and notifies systemd-resolved in a more direct way without
requiring restarting, and so doesn't trigger the restart limiting.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1939255/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
