Description of problem:
Programs that use NM can benefit from marking a connection profile with a label/tag.
One simple usage is to mark a connection as "owned" by the program the uses NM, allowing such a program to differentiate between connections it manages and others which it does not.
Such a label can be generalized to user-data field/s, allowing the user/program add limited information for its own use (ignored by NM).
please review: th/user-data-v2-bgo776276
nmcli support is still missing.
now, the only thing missing is nmcli support.
That will not make it to rhel-7.4 and is left for later.
I am moving this bug to MODIFIED, as the core parts will be in rhel-7.4:
- libnm support
- support from the daemon, including keyfile and ifcfg-rh settings plugin to
persist the user-data.
As nmcli support is not yet implemented, you might want to use the example script https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/examples/python/gi/setting-user-data.py?id=0b6490f3d88c58597f288b63ed7e6d51ca21f2bf
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.