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:
device state: NM_DEVICE_STATE_UNMANAGED
Version-Release number of selected component (if applicable):
The NM is built from master(f2dbf8fbc0efd3853100c6e7d7187d649e792793)
with fix from
Steps to Reproduce:
1. Use nmstate to create OVS bridge with 1 internal interface and 1 system interface.
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
Gris, could you test the patch in the merge request? I tried the reproducer and did 500 iterations without errors.
I still hit NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_DISCONNECTED error on RHEL 8.2:
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.