This bug was fixed in the package systemd - 245.4-4ubuntu3.13
---------------
systemd (245.4-4ubuntu3.13) focal; urgency=medium
* d/p/dell-clamshell-accel-location-base-with-sku.patch:
Revert incorrect patch (LP: #1942899)
systemd (245.4-4ubuntu3.12) focal; urgency=medium
[ Yao Wei ]
* d/p/dell-clamshell-accel-location-base.patch:
Add ACCEL_LOCATION=base property for Dell clamshell models (LP: #1938259)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5c1be33900edee94da0dc9a4ade8edcd079b4c85
[ Lukas Märdian ]
* Add d/p/lp1934221-resolved-disable-event-sources-before-unreffing-them.patch
- Fix segfault in systemd-resolve (LP: #1934221)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6c401900c70962052f56c7108fdc02fe7f84c9bf
[ Simon Chopin ]
* d/p/lp1914740-network-enable-DHCP-broadcast-flag-if-required-by-in.patch:
- Apply upstream patch to fix Hipersocket DHCP mode (LP: #1914740)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=326ae43b7966d9e7c5f7124027185a79a07fa276
[ Dan Streetman ]
* 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=997f3a7da3d5db22e3c63626c3f7dc3dff0830b0
* d/p/lp1937238-util-return-the-correct-correct-wd-from-inotify-help.patch:
Fix watch for time sync (LP: #1937238)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=dbabff8a03eb232c19174eff1335cd7cb7d7860c
* 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=9d3a91a0b70a4b2bcc166f366cd0a880fd494812
* d/p/lp1935051-shared-unit-file-make-sure-the-old-hashmaps-and-sets.patch:
Fix memory leak in path cache (LP: #1935051)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=12d6bdeb35f309158fe8d4242c6dd9be4d067604
*
d/p/lp1934147/0001-cgroup-do-catchup-for-unit-cgroup-inotify-watch-file.patch,
d/p/lp1934147/0002-core-Make-sure-cgroup_oom_queue-is-flushed-on-manage.patch:
Catchup cgroup inotify watch after reexec/reload (LP: #1934147)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=63eabc88b8e0005eb40b15b543538ce35377bdbd
-- Dan Streetman <ddstr...@canonical.com> Tue, 07 Sep 2021 14:37:22
-0400
--
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
