Bug 2186212
| Summary: | Cable unplugged - existing connection was assumed | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Peter Kopec <pekopec> | ||||||||||
| Component: | NetworkManager | Assignee: | Thomas Haller <thaller> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Filip Pokryvka <fpokryvk> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 9.3 | CC: | bgalvani, lrintel, rkhan, sfaye, sukulkar, thaller, till, tpelka, vbenes, zkabelac | ||||||||||
| Target Milestone: | rc | Keywords: | Triaged | ||||||||||
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | NetworkManager-1.43.8-1.el9 | Doc Type: | No Doc Update | ||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2023-11-07 08:38:04 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: |
|
||||||||||||
@zkabelac has found and upstream issue which looks identical to this, adding link here for awareness. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1265 Could you please attach a complete `level=TRACE` log? See the DEBUGGING section in `man NetworkManager` about logging. Also, how does the non-working case compare in the log to version 1.42.2-1? Do you have a log from that too? When the non-working state is reached, what is the output of `nmcli device` and `nmcli connection` ? and what gives `ip link` in that case? Created attachment 1958622 [details]
debug NM 1.43
Created attachment 1958623 [details]
debug NM 1.42
Created attachment 1958624 [details]
nmcli and IP output
I have attached all the logs. All logs are captured after suspend resume cycle. this was a regression in 1.43.3 ([1]) and fixed in 1.43.8 ([2]) [1] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/5a9a7623c5a4bae2001b30eb99e640e2e3285c3e [2] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/5e3bef6ae9f8441a95767191b829d0d57673506c it's also reported against Fedora 39 as bug 2193422. Thank you Peter, for the report!! Verifying, tested manually so far, test will follow-up soon. 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 (NetworkManager bug fix and enhancement update), 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-2023:6585 |
Created attachment 1957143 [details] NM log Description of problem: After suspend resume cycle internet connection is not working - GCC is saying "Unavailable - existing connection was assumed". Restating Network Manager will restore internet connection. There is no issue with NetworkManager-1:1.42.2-1.el9.x86_64. Version-Release number of selected component (if applicable): NetworkManager-1.43.4-1.el9.x86_64 How reproducible: 100% Attaching Network manager journal log.