Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Created attachment 1650018 [details]
System logs with NM trace enabled

Description of problem:

When activating a OVS internal internal after its port been activated,

I got state-change callback on NM.ActivateConnection with:

      reason: NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_DISCONNECTED
      device state: NM_DEVICE_STATE_UNMANAGED



Version-Release number of selected component (if applicable):

The NM is built from master(f2dbf8fbc0efd3853100c6e7d7187d649e792793)
with fix from
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/358


How reproducible:
10%

Steps to Reproduce:
1. Use nmstate to create OVS bridge with 1 internal interface and 1 system interface.
2.
3.

Actual results:

Activation failed.


Expected results:

No failure

Additional info:

Hi Beniamino,

This problem still exists in NetworkManager-1.22.7-24666.dbd7083881.el8.x86_64

Any update on this?

You may use the same reproducer in bug #1781165

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/412

Gris, could you test the patch in the merge request? I tried the reproducer and did 500 iterations without errors.

Hi Beniamino,

I still hit NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_DISCONNECTED error on RHEL 8.2:

NetworkManager-1.23.1-24994.49472438cd.el8.x86_64
openvswitch2.12-2.12.0-12.el8fdp.x86_64
kernel-4.18.0-167.el8.x86_64

Created attachment 1663114 [details]
System logs with NM trace enabled (NetworkManager-1.23.1-24994.49472438cd.el8)

Thanks Gris, I found another issue. Can you please test the additional patch in the MR?

Created attachment 1663535 [details]
System logs with NM trace enabled (NetworkManager-1.23.1-25012.38977d8dcc.el8.x86_64)

Still have the NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_DISCONNECTED problem.

covered by the nmstate test executing nmstate's CI.

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, 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-2020:1847