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.

Description of problem:
I just created basic connection profile to 802.1x (no matter if TLS, PEAP, TTLS), then clicked Available to all users and clicked apply. Profile disappeared but it's correctly stored in ifcfg file.

so if ifcfg file contains KEY_MGMT=IEEE8021X

then nm cannot see it 

Version-Release number of selected component (if applicable):
NetworkManager-0.8.1-32.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1.create new 802.1x wired profile
2.click available to all users and click apply

  
Actual results:
profile not longer available in nm-connection-editor
stored correctly into ifcfg file

Expected results:
correct ifcfg file
and profile visible in nm

Additional info:

the same is happening when using wireless networking and enterprise encryption types