Hide Forgot
Description of problem: When activation a OVS internal interface, it might get error: error=nm-client-error-quark: Active connection removed before it was initialized Version-Release number of selected component (if applicable): NetworkManager-1.20.0-3.el8.x86_64 openvswitch2.11-2.11.0-26.el8fdp.x86_64 nmstate-0.2.0-2.el8 How reproducible: 10% Steps to Reproduce: * sudo bash ./ovs_bug.sh Actual results: NM main-loop aborted: Connection activation failed on connection_id ovs0: error=nm-client-error-quark: Active connection removed before it was initialized (2) Expected results: No failure. Additional info: You might also get failure on timeout hanging at NM_ACTIVE_CONNECTION_STATE_ACTIVATING of ovs0 interface. I am still debugging it to find out which part(nmstate or NM) might be wrong, please ignore and start another round of reproduce script.
Created attachment 1643294 [details] ovs_bug.sh Reproduce script.
Created attachment 1643295 [details] yml file required to reproduce problem.
Created attachment 1643296 [details] System logs with NM trace enabled
Created attachment 1643298 [details] ovs_bug.sh Reproduce script
> <info> [1575895006.1154] device (ovs0): state change: deactivating -> ip-config (reason 'none', sys-iface-state: 'managed') this looks wrong.
(In reply to Thomas Haller from comment #5) > > <info> [1575895006.1154] device (ovs0): state change: deactivating -> ip-config (reason 'none', sys-iface-state: 'managed') > > this looks wrong. Anything should I do in nmstate?
(In reply to Gris Ge from comment #6) > (In reply to Thomas Haller from comment #5) > > > <info> [1575895006.1154] device (ovs0): state change: deactivating -> ip-config (reason 'none', sys-iface-state: 'managed') > > > > this looks wrong. > > Anything should I do in nmstate? No, it's a bug in NM. The branch at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/358 should fix the state-change problem. It's not clear whether that problem is the cause of the activation failure. Gris, would you be able to test that NM branch? Should I prepare a scratch build?
(In reply to Beniamino Galvani from comment #7) > (In reply to Gris Ge from comment #6) > > (In reply to Thomas Haller from comment #5) > > > > <info> [1575895006.1154] device (ovs0): state change: deactivating -> ip-config (reason 'none', sys-iface-state: 'managed') > > > > > > this looks wrong. > > > > Anything should I do in nmstate? > > No, it's a bug in NM. > > The branch at > https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/ > 358 should fix the state-change problem. It's not clear whether that problem > is the cause of the activation failure. > > Gris, would you be able to test that NM branch? Should I prepare a scratch > build? Hi Beniamino, Thanks for the quick fix. With your patch, I never see `Active connection removed before it was initialized (2)` error anymore. Even through there are many other errors which I will create bug to track them soon.
Fixed by: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/0738c1044524b938f008c111b829db7dabbb8269
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