RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

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

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.

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).

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

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