Bug 1625901

Summary:	NM starts a DHCP grace period even if the DHCP client is not running
Product:	Red Hat Enterprise Linux 8	Reporter:	Beniamino Galvani <bgalvani>
Component:	NetworkManager	Assignee:	NetworkManager Development Team <nm-team>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.3	CC:	acardace, atragler, bgalvani, fgiudici, fpokryvk, lrintel, mboisver, pasik, rkhan, sukulkar, thaller, till, vbenes
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.0	Flags:	pm-rhel: mirror+
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:	2021-01-08 07:35:17 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 Beniamino Galvani 2018-09-06 08:11:17 UTC

NM starts a DHCP grace period even if the DHCP client is not running. Instead it should detect that the client terminated and fail the connection, or proceed without waiting.

See here for more details and logs:
https://bugzilla.redhat.com/show_bug.cgi?id=1578668#c4

Comment 2 Beniamino Galvani 2018-10-15 16:11:17 UTC

Fixed upstream:

https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=89caba77cbcdc1bb2160e0012c412c2458445b56

Comment 4 Filip Pokryvka 2019-05-22 15:12:24 UTC

Consider the following scenario with main.dhcp=dhclient:

    * Prepare simulated test "testX4" device
    * Add connection type "ethernet" named "con_ipv4" for device "testX4"
    * Modify connection "con_ipv4" changing options "ipv4.may-fail no"
    * Bring "down" connection "con_ipv4"
    * Note dhclient pids
    * Bring "up" connection "con_ipv4"
    When "con_ipv4" is visible with command "nmcli con show -a" in "10" seconds
    * Wait for at least "10" seconds
    * Execute "mv /usr/sbin/dhclient /usr/sbin/dhclient-tmp"
    * Execute "cp /usr/bin/false /usr/sbin/dhclient"
    * Kill dhclient with not noted pid

After this, when IPv4 expires on testX4 (it is not renewed, because dhclient always fails), connection con_ipv4 stays active. The connection should fail, when IPv4 lease expires and there is no dhclient running.

Comment 8 Thomas Haller 2020-08-19 11:01:18 UTC

moving to rhel-8, as rhel-7 will only get "important" fixes.

Comment 14 RHEL Program Management 2021-01-08 07:35:17 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.