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 1066703 is about improving how we model network configuration in NetworkManager, in particular how we model devices.

currently, NMDevice does too many things. A NMDevice instance is itself exported on D-Bus (it is-a NMDBusObject). But it also implements most of the relevant handling for IP configuration.

In a first step, refactor the IP configuration and make it independent of NMDevice. For that, introduce a new class NML3Cfg and NML3ConfigData which are responsible for tracking and applying IP configuration. NML3ConfigData wil in parts replace NMIP4Config/NMIP6Config, which also has too many responsibilities (being also an NMDBusObject and tracking configuration).


This is already WIP. More work is necessary.

current work in progress is branch "th/l3cfg-??" (where ?? is a number).

That last branch contains one commit that changes in large parts the state handling of NMDevice. It will starting using NML3Cfg, NML3ConfigData, NML3IPv4LL, and thereby replace NMIP[46]Config. It also needs to entirely rework the handling of the activation state.

Doing that, is one huge commit. It cannot be split into smaller parts, because once you start changing NMDevice implementation, it all needs to be reworked together.

The work is done, when the last "th/l3cfg-??" gets merged to master.


Moving back to ASSIGNED.

the branch is now just called "next", as this is the next major rework of NetworkManager. Still WIP.

It has been tested by running multiple CI jobs and doing a performance test.

We see some minor glitches but overall results are good.

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/RHEA-2022:1985