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 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.

@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