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.

when a device is configured outside of NM, NetworkManager generates an in-memory connection and pretends that to be active (but it doesn't actually touch the device). 

This is tricky for various reasons. See bug 1650221 for how to improve that overall.


The worst is that this is really unclear to users. They look at `nmcli connection` output and see there the device and profiles that look like regular profiles. Thinking that NetworkManager configures the device.

We should make it clear in the UI (nmcli) that these devices/profiles are special. Possibly by coloring them in dark colors (or grey). That many require extension on D-Bus API.


This bug is about improving the user experience and highlight that something special is going on. It also may apply to nmtui...

> This is tricky for various reasons. See bug 1650221 for how to improve that overall.

I meant bug 1616363

WIP: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/533

some tests fixed to reflect connected (externally) in nmcli output
https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/merge_requests/580
    bug filed:
    https://bugzilla.redhat.com/show_bug.cgi?id=1848460

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