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 2063109 - [Rebase] Rebase NetworkManager to latest upstream release in RHEL 8.7
Summary: [Rebase] Rebase NetworkManager to latest upstream release in RHEL 8.7
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Vojtěch Bůbela
QA Contact: Vladimir Benes
Marc Muehlfeld
Depends On:
TreeView+ depends on / blocked
Reported: 2022-03-11 09:56 UTC by Beniamino Galvani
Modified: 2022-11-08 11:15 UTC (History)
9 users (show)

Fixed In Version: NetworkManager-1.40.0-1.el8
Doc Type: Enhancement
Doc Text:
.NetworkManager rebased to version 1.40 The `NetworkManager` packages have been upgraded to upstream version 1.40, which provides a number of enhancements and bug fixes over the previous version: * The device state files in the `/run/NetworkManager/devices/` directory now have new sections, `[dhcp4]` and `[dhcp6]`, which contain the DHCP options of the current lease. * NetworkManager supports setting an IPv6 Maximum Transmission Unit (MTU) in the `ipv6.mtu` property of connections. * NetworkManager uses the `nm.debug` kernel command line option to enable debug logging. * Carrier detection has been improved. * NetworkManager now restarts the DHCP client for a connection if the MAC address changes on a device. * Wifi hotspots now use a stable random channel number unless you select a specific channel. * NetworkManager now disables the Wi-Fi Protected Access 3 (WPA3) transition mode if you set the `wifi.key-mgmt` property to `wpa-psk` and the network interface does not support Protected Management Frames (PMF). The transition mode caused problems in certain setups in this scenario. To explicitly enable the WPA3 transitioning mode, set `wifi.key-mgmt` to `sae`. * NetworkManager now shortens an excessively long hostname received from a DHCP server to the first dot or to 64 characters. For further information about notable changes, read the link:https://github.com/NetworkManager/NetworkManager/blob/nm-1-40/NEWS[upstream release notes].
Clone Of:
Last Closed: 2022-11-08 10:07:32 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-115320 0 None None None 2022-03-11 09:59:17 UTC
Red Hat Product Errata RHBA-2022:7680 0 None None None 2022-11-08 10:08:14 UTC

Description Beniamino Galvani 2022-03-11 09:56:49 UTC
Rebase NetworkManager to the latest upstream stable release for 8.7 to get new features and bug fixes.

Comment 10 Thomas Haller 2022-08-31 17:46:30 UTC
> * NetworkManager prefers the first static IPv6 addresses from the `ipv6.addresses` property and the order was inverted to be consistent with how NetworkManager handles multiple IPv4 addresses in a connection pro

This is correct for upstream and rhel-9.1, but in rhel-8 we reverted this part to not change behavior. rhel-9.1 will get this new behavior.
See bug 2097293 (RHEL-9.1) and bug 2097270 (RHEL-8.7) which are about this very thing. Just drop this point for 8.7 (but not 9.1).

the rest lgtm.

Comment 15 errata-xmlrpc 2022-11-08 10:07:32 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.


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