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.
Bug 1781165 - NM OVS: Active connection removed before it was initialized
Summary: NM OVS: Active connection removed before it was initialized
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: sushil kulkarni
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: nmstate-nm
TreeView+ depends on / blocked
 
Reported: 2019-12-09 12:58 UTC by Gris Ge
Modified: 2023-02-12 20:48 UTC (History)
8 users (show)

Fixed In Version: NetworkManager-1.22.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:53:59 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
ovs_bug.sh (328 bytes, application/x-shellscript)
2019-12-09 12:59 UTC, Gris Ge 		no flags Details
yml file required to reproduce problem. (445 bytes, text/plain)
2019-12-09 13:00 UTC, Gris Ge 		no flags Details
System logs with NM trace enabled (621.62 KB, text/plain)
2019-12-09 13:00 UTC, Gris Ge 		no flags Details
ovs_bug.sh (318 bytes, application/x-shellscript)
2019-12-09 13:28 UTC, Gris Ge 		no flags Details
Show Obsolete (1) View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-279 0 None None None 2023-02-12 20:48:59 UTC
Red Hat Issue Tracker RHELPLAN-37447 0 None None None 2023-02-12 20:46:02 UTC
Red Hat Product Errata RHBA-2020:1847 0 None None None 2020-04-28 16:54:24 UTC

Description Gris Ge 2019-12-09 12:58:42 UTC 
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.
Comment 1 Gris Ge 2019-12-09 12:59:31 UTC 
Created attachment 1643294 [details]
ovs_bug.sh

Reproduce script.
Comment 2 Gris Ge 2019-12-09 13:00:25 UTC 
Created attachment 1643295 [details]
yml file required to reproduce problem.
Comment 3 Gris Ge 2019-12-09 13:00:59 UTC 
Created attachment 1643296 [details]
System logs with NM trace enabled
Comment 4 Gris Ge 2019-12-09 13:28:49 UTC 
Created attachment 1643298 [details]
ovs_bug.sh

Reproduce script
Comment 5 Thomas Haller 2019-12-09 15:49:11 UTC 
> <info>  [1575895006.1154] device (ovs0): state change: deactivating -> ip-config (reason 'none', sys-iface-state: 'managed')

this looks wrong.
Comment 6 Gris Ge 2019-12-10 13:08:08 UTC 
(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?
Comment 7 Beniamino Galvani 2019-12-11 12:32:01 UTC 
(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?
Comment 8 Gris Ge 2019-12-12 06:03:46 UTC 
(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.
Comment 9 Beniamino Galvani 2019-12-14 20:14:04 UTC 
Fixed by: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/0738c1044524b938f008c111b829db7dabbb8269
Comment 13 Vladimir Benes 2020-02-21 12:12:22 UTC 
covered by the nmstate test executing nmstate's CI.
Comment 15 errata-xmlrpc 2020-04-28 16:53:59 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, 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
Note You need to log in before you can comment on or make changes to this bug.