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...
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