Bug 2077752

Summary:	ensure proper retry/restart with DHCP client
Product:	Red Hat Enterprise Linux 9	Reporter:	Thomas Haller <thaller>
Component:	NetworkManager	Assignee:	NetworkManager Development Team <nm-team>
Status:	CLOSED DUPLICATE	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.1	CC:	bgalvani, lrintel, miabbott, rkhan, sdodson, sukulkar, till
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-26 16:29:24 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:
Bug Depends On:
Bug Blocks:	2077605

Description Thomas Haller 2022-04-22 06:37:26 UTC

with "next" rework, we also aimed to simplify the internal DHCP API in NetworkManager.

This is bug 2001986, and also described also at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/26a0307b8fb0f9b2f6fc14e29e45c5d9a176e479/src/core/README.l3cfg.md#dhcp .



This means, `NMDhcpClient` needs to try hard to abstract all failures from the upper layers, and to proper restart/retry.

From https://bugzilla.redhat.com/show_bug.cgi?id=2077605#c4, it seems this might not always happen correctly. Investigate and possibly fix.

Comment 1 Thomas Haller 2022-04-26 16:29:24 UTC

ok, I am gonna close this as duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2077605#c4 .
As that bug already has additional information, but is essentially about the same problem.

*** This bug has been marked as a duplicate of bug 2077605 ***