Bug 1782701
| Summary: | NM OVS: Hang at NM_ACTIVE_CONNECTION_STATE_ACTIVATING state for ovs internal port | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Gris Ge <fge> | ||||||
| Component: | NetworkManager | Assignee: | Beniamino Galvani <bgalvani> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 8.2 | CC: | acardace, atragler, bgalvani, lrintel, rkhan, sukulkar, thaller, vbenes | ||||||
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
||||||
| Target Release: | 8.2 | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | NetworkManager-1.22.8-1.el8 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-04-28 16:53:59 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Gris Ge
2019-12-12 07:32:40 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. Created attachment 1645580 [details]
System logs with NM trace enabled (NetworkManager-1.23.0-24609.1e9ab78bfc)
Hopefully the issue is fixed by https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/402 Hi Gris, can you please check if the patch above fixes the problem? Upstream fix: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/623a1e1f993b3166509202bc580c30e3daf9c67b Hi Beniamino, With NetworkManager-1.22.7-24666.dbd7083881.el8.x86_64, I got no NM_ACTIVE_CONNECTION_STATE_ACTIVATING hang failure. Thanks. 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 |