Bug 2186212 - Cable unplugged - existing connection was assumed
Summary: Cable unplugged - existing connection was assumed
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: NetworkManager
Version: 9.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: Filip Pokryvka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-12 12:30 UTC by Peter Kopec
Modified: 2023-08-01 09:29 UTC (History)
10 users (show)

Fixed In Version: NetworkManager-1.43.8-1.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
NM log (9.69 KB, text/plain)
2023-04-12 12:30 UTC, Peter Kopec
no flags Details
debug NM 1.43 (297.12 KB, text/plain)
2023-04-20 15:43 UTC, Peter Kopec
no flags Details
debug NM 1.42 (372.07 KB, text/plain)
2023-04-20 15:44 UTC, Peter Kopec
no flags Details
nmcli and IP output (334 bytes, text/plain)
2023-04-20 15:45 UTC, Peter Kopec
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-474 0 None None None 2023-04-12 12:31:17 UTC
Red Hat Issue Tracker RHELPLAN-154527 0 None None None 2023-04-12 12:31:22 UTC
freedesktop.org Gitlab NetworkManager NetworkManager-ci merge_requests 1466/ 0 None None None 2023-08-01 09:29:06 UTC

Description Peter Kopec 2023-04-12 12:30:44 UTC
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.

Comment 1 Peter Kopec 2023-04-19 10:55:56 UTC
@zkabelac has found and upstream issue which looks identical to this, adding link here for awareness.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1265

Comment 2 Thomas Haller 2023-04-19 14:02:28 UTC
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` ?

Comment 3 Thomas Haller 2023-04-19 14:04:32 UTC
and what gives `ip link` in that case?

Comment 4 Peter Kopec 2023-04-20 15:43:33 UTC
Created attachment 1958622 [details]
debug NM 1.43

Comment 5 Peter Kopec 2023-04-20 15:44:20 UTC
Created attachment 1958623 [details]
debug NM 1.42

Comment 6 Peter Kopec 2023-04-20 15:45:31 UTC
Created attachment 1958624 [details]
nmcli and IP output

Comment 7 Peter Kopec 2023-04-20 15:47:25 UTC
I have attached all the logs. All logs are captured after suspend resume cycle.

Comment 12 Thomas Haller 2023-06-06 13:53:49 UTC
Thank you Peter, for the report!!

Comment 14 Filip Pokryvka 2023-08-01 09:11:16 UTC
Verifying, tested manually so far, test will follow-up soon.


Note You need to log in before you can comment on or make changes to this bug.