> It seems this issue may occur not only when receiving addresses on
multiple interfaces, but also when dhcp requests on multiple interfaces
times out and the hook script was called with 'reason' == FAIL.
yep, the try-reload-or-restart is done for those as well and this should
be fixed for those $
Hi. It seems this issue may occur not only when receiving addresses on multiple
interfaces, but also when dhcp requests on multiple interfaces times out and
the hook script was called with 'reason' == FAIL.
Found on Ubuntu 20.04.3 LTS, systemd is 245.4-4ubuntu3.15.
** Attachment added: "DHCPDISC
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-co
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 ]
as systemd was respun (for focal) due to bug 1942899, and only the one
udev (hwdb) patch was reverted which shouldn't affect this at all, I'm
remarking this as verified still based on testing for the previous
version above.
** Tags removed: verification-needed verification-needed-focal
** Tags ad
Hello Dan, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.13 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
ubuntu@lp1939255-b:~$ dpkg -l systemd|grep systemd
ii systemd237-3ubuntu10.51 amd64system and service manager
ubuntu@lp1939255-b:~$ sudo dhclient ens8 ens9 ens10 ens11 ens12 ens13 ens14
ens15
ubuntu@lp1939255-b:~$ journalctl --no-pager -b -u systemd-resolved
-- Logs begin at Sun 2
ubuntu@lp1939255-f:~$ dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.11 amd64system and service manager
ubuntu@lp1939255-f:~$ sudo dhclient ens8 ens9 ens10 ens11 ens12 ens13 ens14
ens15
ubuntu@lp1939255-f:~$ journalctl --no-pager -b -u systemd-resolved
-- Logs begin at Sun
Hello Dan, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.12 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Hello Dan, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.52 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
I have tested this on both Focal and Bionic VMs. I ensured that the
systemd-resolved unit was in a failed state, restarted it, added the
PPA, updated the systemd packages, and rebooted. After every reboot the
systemd-resolved was in an "active" state.
I tested this with at least 10 reboots on each
11 matches
Mail list logo
