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 1644314[details]
System logs with NM trace enabled
Description of problem:
When activating OVS internal port, activating hang at
NM_ACTIVE_CONNECTION_STATE_ACTIVATING without further
signal callback on `state-change` of neither device or acticate connection.
Version-Release number of selected component (if applicable):
NetworkManager-1.23.0-24592.affd60a91c.el8.x86_64
# master of NM with fix of bug #1781165
nmstate-0.2.0-2.el8
How reproducible:
10%
Steps to Reproduce:
1. Please use the same reproduce script of bug 1781165
2.
3.
Actual results:
nmstate hang at NM_ACTIVE_CONNECTION_STATE_ACTIVATING for 30 seconds.
Expected results:
No failure.
Additional info:
Comment 1Beniamino Galvani
2019-12-16 09:03:22 UTC
Hi Gris,
I wasn't able to understand the reason of the hang from the logs attached, and I can't reproduce the issue either.
I have prepared branch bg/rh1782701 of NM with additional debugging log messages; could you please reproduce the problem with that NM version and attach logs? Thanks!
(In reply to Beniamino Galvani from comment #1)
> Hi Gris,
>
> I wasn't able to understand the reason of the hang from the logs attached,
> and I can't reproduce the issue either.
nmstate is waiting on `state-change` signal from NM.Device or NM.ActivateConnection.
But nmstate failed to get callback for 30 seconds and the activation
stuck at NM_ACTIVE_CONNECTION_STATE_ACTIVATING.
You need to try many times before hit this problem.
>
> I have prepared branch bg/rh1782701 of NM with additional debugging log
> messages; could you please reproduce the problem with that NM version and
> attach logs? Thanks!
Will do.
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