[Bug 1907306] Re: networkd dhcpv4 client never attempts more than 2 renew and 2 rebind

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 237-3ubuntu10.44

---------------
systemd (237-3ubuntu10.44) bionic; urgency=medium

  * d/extra/dhclient-enter-resolved-hook:
    suppress output of cmp command in dhclient hook (LP: #1878955)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c5a2db69aafc7a3ab4e71bae44fd7ad9dd955c97
  * d/p/lp1905044/0001-capability-add-a-way-to-get-a-uint64_t-with-all-caps.patch,
    d/p/lp1905044/0002-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=34ebc6e28e63881d40c91c5839597acc2fdab546
  * d/p/lp1905245/0001-basic-cap-list-parse-print-numerical-capabilities.patch:
    print number of unknown capabilities instead of failing
    (LP: #1905245)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5ab225b7f731c6cf6b4655cb27c3a842150c4c1a
  * 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/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=036230cac8232bf4f970e565c355ee1a82fc2ee6
  * d/t/root-unittests:
    Remove any corrupt journal files (LP: #1881947)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b284b93e40b6cb834bb40dd3db94850853ab5bb8

 -- Dan Streetman <ddstreet at canonical.com>  Wed, 06 Jan 2021 16:04:25
-0500

** Changed in: systemd (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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 Released
Status in systemd source package in Focal:
  Fix Released
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