Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1421429

Summary: [RFE] Connection profile user data
Product: Red Hat Enterprise Linux 7 Reporter: Edward Haas <edwardh>
Component: NetworkManagerAssignee: Thomas Haller <thaller>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: aloughla, atragler, bgalvani, danken, fgiudici, lrintel, mleitner, rkhan, sukulkar, thaller, vbenes, ylavi
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.8.0-1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 09:22:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Edward Haas 2017-02-12 09:47:25 UTC
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).

Comment 2 Thomas Haller 2017-05-05 09:13:32 UTC
please review: th/user-data-v2-bgo776276

nmcli support is still missing.

Comment 3 Thomas Haller 2017-05-06 13:04:19 UTC
merged:

master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=0b6490f3d88c58597f288b63ed7e6d51ca21f2bf

nm-1-8: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=fd6f4b0ef8bec0569d2227f67d77a161ca916858



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

Comment 7 errata-xmlrpc 2017-08-01 09:22:07 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, 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/RHSA-2017:2299