Bug 2027267
| Summary: | NetworkManager-1.34.0-0.3 not renewing DHCPv6 leases when using internal DHCP client | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Daniel Juarez <djuarezg> |
| Component: | NetworkManager | Assignee: | Thomas Haller <thaller> |
| Status: | CLOSED ERRATA | QA Contact: | David Jaša <djasa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | CentOS Stream | CC: | alex.iribarren, bgalvani, bstinson, djuarezg, ferferna, jwboyer, lrintel, nacho.barrientos, rkhan, sukulkar, thaller, till, vbenes |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | NetworkManager-1.36.0-0.2.el8 | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-10 14:54:52 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Daniel Juarez
2021-11-29 09:19:17 UTC
For extra reference, https://github.com/NetworkManager/NetworkManager/commit/51f93e00a23fbd09f5ad96da6290bf4ca737d46a modifies dhpc6 related code The problem seems to be how .3 calculates the T1 and T2 timers. NetworkManager-1.34.0-0.3 Nov 29 11:31:24 test134003.cern.ch NetworkManager[950]: <trace> [1638181884.6690] libsystemd: eth0: DHCPv6 client: T1 expires in 34y 2w 1d 2h 27min 32s Nov 29 11:31:24 test134003.cern.ch NetworkManager[950]: <trace> [1638181884.6689] libsystemd: eth0: DHCPv6 client: Received an IA option with both T1 and T2 equal to zero. Adjusting them based on the minimum valid lifetime of IA addresses or PD prefixes: T1=1075643520sec, T2=1721029632sec Nov 29 11:31:24 test134003.cern.ch NetworkManager[950]: <trace> [1638181884.6690] libsystemd: eth0: DHCPv6 client: T1 expires in 34y 2w 1d 2h 27min 32s Nov 29 11:31:24 test134003.cern.ch NetworkManager[950]: <trace> [1638181884.6690] libsystemd: eth0: DHCPv6 client: T2 expires in 54y 5month 3w 5d 19h 35min 36s NetworkManager-1.34.0-0.2 Nov 29 11:37:17 test134002.cern.ch NetworkManager[893]: <trace> [1638182237.3446] libsystemd: eth0: DHCPv6 client: Recv ADVERTISE Nov 29 11:37:18 test134002.cern.ch NetworkManager[893]: <trace> [1638182238.3721] libsystemd: eth0: DHCPv6 client: Sent REQUEST Nov 29 11:37:18 test134002.cern.ch NetworkManager[893]: <trace> [1638182238.3722] libsystemd: eth0: DHCPv6 client: Next retransmission in 995ms Nov 29 11:37:18 test134002.cern.ch NetworkManager[893]: <trace> [1638182238.4773] libsystemd: eth0: DHCPv6 client: Computed IA NA T1 302400sec and T2 483840sec as both were zero Nov 29 11:37:18 test134002.cern.ch NetworkManager[893]: <trace> [1638182238.4775] libsystemd: eth0: DHCPv6 client: T1 expires in 3d 7h 30min Nov 29 11:37:18 test134002.cern.ch NetworkManager[893]: <trace> [1638182238.4775] libsystemd: eth0: DHCPv6 client: T2 expires in 5d 3h 59min 13s So in other words .3 sets the T1 timer to an stupid value, explaining why it never issues any request to renew the lease. To get the logging above set: level=TRACE domains=ALL in /etc/NetworkManager/NetworkManager.conf. To be determine if this is a bug (probably introduced here: https://github.com/NetworkManager/NetworkManager/commit/51f93e00a23fbd09f5ad96da6290bf4ca737d46a) or a behavior change and the client now expects more info from the server. Related code: https://github.com/NetworkManager/NetworkManager/blob/29380a0b099cc8ad50fc8471285b4c9a07b2cdce/src/libnm-systemd-core/src/libsystemd-network/dhcp6-option.c#L688 We believe we've tracked down the issue and we've submitted a patch upstream: https://github.com/systemd/systemd/pull/21558 Once this patch is merged, what's the procedure for getting it into CS8? For reference we also filed an issue on https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/863 where RedHat contributions are also done. The fix mentioned above is distributed by NetworkManager-1.36.0-0.2 onwards (which contains NM 1.35.2-dev). Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (NetworkManager bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2022:1985 |