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.
Bug 2169512 - Better handle netlink error 'too many netlink events'
Summary: Better handle netlink error 'too many netlink events'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: NetworkManager
Version: 9.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: David Jaša
URL:
Whiteboard:
Depends On: 2154350
Blocks: 2183217
TreeView+ depends on / blocked
 
Reported: 2023-02-13 20:02 UTC by Thomas Haller
Modified: 2023-11-07 10:13 UTC (History)
14 users (show)

Fixed In Version: NetworkManager-1.43.5-1.el9
Doc Type: No Doc Update
Doc Text:
Clone Of: 2154350
Environment:
Last Closed: 2023-11-07 08:37:57 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-360 0 None None None 2023-03-06 07:51:05 UTC
Red Hat Issue Tracker RHELPLAN-148523 0 None None None 2023-02-13 20:02:54 UTC
Red Hat Product Errata RHBA-2023:6585 0 None None None 2023-11-07 08:38:29 UTC
freedesktop.org Gitlab NetworkManager NetworkManager-ci merge_requests 1432 0 None opened test if NM doesn't lose netlink messages related to its own L3 requests 2023-05-30 09:41:47 UTC
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 1537 0 None opened Retry when platform went out of sync while sending a command 2023-03-14 15:02:52 UTC

Description Thomas Haller 2023-02-13 20:02:28 UTC
+++ This bug was initially created as a clone of Bug #2154350 +++

when the netlink receive buffer overflows, we need to resync and loose messages.

Thereby, we might also loose a reply to a request that we made, which causes the operation to fail.

In bug 2154350 and upstream [1], this was fixed for link requests.

[1] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/38d3834e2c464bd4820392800a3a1fe3f286fc62

But for ther netlink requests (e.g. adding an ip address), this is still now working correctly. See https://bugzilla.redhat.com/show_bug.cgi?id=2154350#c5


This bug exists to fix the related issues.

Comment 11 David Jaša 2023-05-30 06:33:38 UTC
VERIFIED in NetworkManager-1.43.8-1.el9: even in "too many netlink events" condition, NM doesn't lose track of IP configuration of interfaces.

Comment 17 errata-xmlrpc 2023-11-07 08:37:57 UTC
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


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