Bug 2079298

Summary:	Backport into RHEL 8.8 fix for Bug 2050216 - Device is failing on DHCPv4 after NM restart
Product:	Red Hat Enterprise Linux 8	Reporter:	Yurii Prokulevych <yprokule>
Component:	NetworkManager	Assignee:	Beniamino Galvani <bgalvani>
Status:	CLOSED ERRATA	QA Contact:	David Jaša <djasa>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	8.5	CC:	bgalvani, jcaamano, lrintel, rkhan, sfaye, sukulkar, thaller, till, vbenes
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	NetworkManager-1.40.2-1.el8	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-16 09:04:54 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 Yurii Prokulevych 2022-04-27 10:57:43 UTC

Description of problem:
-----------------------
OCP(4.11.0-0.nightly-2022-04-25-220649) with bonded interfaces failed.

After inspecting logs it seems that restarting NetworkManager immediately after turning networking back on (nmcli network off && nmcli network on &&  systemctl restart NetworkManager) as configure-ovs service does, leaves NM in a state that prevents NM to activate some connections unless they are recycled after (nmcli c down ovs-if-phys0 && nmcli c up ovs-if-phys0)


Version-Release number of selected component (if applicable):
=============================================================
NetworkManager-team-1.32.10-4.el8.x86_64
NetworkManager-1.32.10-4.el8.x86_64
NetworkManager-tui-1.32.10-4.el8.x86_64
NetworkManager-cloud-setup-1.32.10-4.el8.x86_64
NetworkManager-libnm-1.32.10-4.el8.x86_64
NetworkManager-ovs-1.32.10-4.el8.x86_64



Steps to Reproduce:
===================
1. Configure multiple network connections and run
   nmcli network off && nmcli network on &&  systemctl restart NetworkManager


Actual results:
---------------
Some interfaces fail to reactivate


Expected results:
-----------------
All interfaces are successfully reactivated

Comment 2 Yurii Prokulevych 2022-04-27 11:03:18 UTC

Initial investigation done in https://bugzilla.redhat.com/show_bug.cgi?id=2078866

Comment 3 Thomas Haller 2022-04-27 11:15:28 UTC

this is a duplicate of bug 2050216 (which is for RHEL9, but the NetworkManager code is basically the same).

See also https://bugzilla.redhat.com/show_bug.cgi?id=2077605#c4 for more details.

Comment 5 Beniamino Galvani 2022-12-16 09:59:23 UTC

Commit https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/bf5927b978fccec1390bcc7d3d5719d7fe7c3450 is already included in RHEL 8.8 builds of NetworkManager (1.40.2-1 and later).

Comment 8 David Jaša 2023-02-13 22:59:48 UTC

VERIFIED in NetworkManager-1.41.90-1.el9.x86_64: I didn't hit the bug.

Comment 10 errata-xmlrpc 2023-05-16 09:04:54 UTC

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/RHBA-2023:2968