Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
nm-1-26 has two fixes that should be backported to rhel-8.3:
[1] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/cf3cff4f12e78615c18fd829b1f32eac4f607c0b
[2] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/99b362c9443591b2b643aa09980f1a5dd42b1f6b
The problem that [1] fixes is the the following. On D-Bus we expose some IP routes. But for these routes, we don't export the "type" (presumably, they are all of the "unicast" type). Since 1.26, NetworkManager also supports "type local" routes.
The problem is that NM will now also export "type local" routes, but since their type cannot be seen, they look like normal routes. That is wrong.
Eventually we may want to export local routes too, but then we must properly mark their type.
Test: see the routes in `nmcli` output. Note that there are some routes there, that are actually the local types (compare with `ip route`). Patch [1] will remove these routes.
[2] is more subtle. We have a fuzzy understanding what a "default route" is, and in certain (non-clearly defined) situations we take special care of "default routes". Without [2], NetworkManager will also treat /0 routes of "type local" as default route. While all of this is not well defined, it still seems mostly wrong in this context. The fix is simple.
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-2020:4499