This bug was fixed in the package systemd - 246.6-1ubuntu1.1
---------------
systemd (246.6-1ubuntu1.1) groovy; urgency=medium
[ Dan Streetman ]
* d/t/boot-smoke: update test to avoid false negatives
(LP: #1892358)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=205c30ca53b0e421db28bb56afaf5f88650ce592
* d/t/boot-and-services: remove unneeded test lines
(LP: #1892358)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=71853082af4e668996db574915c5a156f9897fd3
* d/t/systemd-fsckd: rewrite test to try to fix false negatives
(LP: #1892358)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6ae6be039ec582410769d2d6d131e12bdcd19a68
* d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch:
test: use cap_last_cap() instead of capability_list_length()
(LP: #1905044)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=84a4832f5f7d4f939c1c78c6be4c3f9e05cd7f59
*
d/p/lp1907306/0001-sd-dhcp-client-don-t-log-timeouts-if-already-expired.patch,
d/p/lp1907306/0002-sd-dhcp-client-track-dhcp4-t1-t2-expire-times.patch,
d/p/lp1907306/0003-sd-dhcp-client-add-RFC2131-retransmission-details.patch,
d/p/lp1907306/0004-sd-dhcp-client-simplify-dhcp4-t1-t2-parsing.patch,
d/p/lp1907306/0005-sd-dhcp-client-correct-dhcpv4-renew-rebind-retransmi.patch,
d/p/lp1907306/0006-sd-dhcp-client-correct-retransmission-timeout-to-mat.patch,
d/p/lp1907306/0007-test-network-increase-wait_online-timeout-to-handle-.patch,
d/p/lp1907306/0008-sd-dhcp-client-fix-renew-rebind-timeout-calculation-.patch:
Send correct number of dhcpv4 renew and rebind requests
(LP: #1907306)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0a96dc16ac00e90cd3904e6d490d676b9bb98f1f
* d/p/lp1902960-udev-re-assign-ID_NET_DRIVER-ID_NET_LINK_FILE-ID_NET.patch:
Run net_setup_link on 'change' uevents (LP: #1902960)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7183e2ef4758ce47b152dec735e7d213d6003e37
* d/t/root-unittests:
Remove any corrupt journal files (LP: #1881947)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3d0ea66f0db4a204759fa0005f6f27579ee4195a
[ Balint Reczey ]
* d/t/systemd-fsckd: Plymouth-start stays active in 20.10 and later
(LP: #1908067)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e3ddd09301c8bdaa59b4fe54d7906f609552370d
-- Dan Streetman <ddstr...@canonical.com> Wed, 06 Jan 2021 15:40:39
-0500
** Changed in: systemd (Ubuntu Groovy)
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/1907306
Title:
networkd dhcpv4 client never attempts more than 2 renew and 2 rebind
Status in systemd:
Fix Released
Status in systemd package in Ubuntu:
In Progress
Status in systemd source package in Bionic:
Fix Committed
Status in systemd source package in Focal:
Fix Committed
Status in systemd source package in Groovy:
Fix Released
Status in systemd source package in Hirsute:
In Progress
Bug description:
[impact]
networkd dhcpv4 client never attempts more than 2 renew and 2 rebind
[test case]
configure an interface to use dhcpv4; acquire a dhcpv4 address, then
stop the dhcpv4 server, and wait for the networkd client to perform
its renewals and rebinds before expiring the lease
using a 20 minute lease time as an example (all times are approximate
due to RFC-mandated random 'fuzz' time of -1 to +1 sec):
the current behavior would be to sent renew requests at:
10:00
13:45
and then rebind requests at:
17:30
18:45
then the lease would expire at 20:00
the correct/new behavior should be renew requests at:
10:00
13:45
15:37
16:37
and then rebind requests at:
17:30
18:45
19:45
and then lease expiration at 20:00.
longer lease times would increase the number of retransmissions.
[regression potential]
any regression would likely result in problems receiving and/or
maintaining a dhcpv4 address
[scope]
this is needed in b/f/g/h.
this was fixed upstream in:
https://github.com/systemd/systemd/pull/17908
that was just added, so this is not fixed in any ubuntu release yet.
technically, this is needed in x as well, however I don't plan to
backport to x since 1) it reaches ESM soon and 2) the default network
management tool in x is ifupdown, not systemd-networkd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1907306/+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
