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:
Don't add wireless network to connection list if user cancels its setup upon first connection

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

How reproducible:
always

Steps to Reproduce:
1. be in range of WEP/WPA network not-yet-known to NM 
2. in nm-applet, click this network
3. quit dialog without actually connecting
  
Actual results:
NM (nm-applet?) adds the network to its connection list

Expected results:
network connection is remembered at actual connection attempt - after user sets up connection details, passphrases etc and _confirms_ them

Additional info:
NM tries to connect to such networks whenever user gets in their range but the user action suggests that user doesn't want to connect to the network at all.

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

In RHEL7 NM will only autoconnect to networks that are successful.  Perhaps we can punt from RHEL6 and call this bug fixed?

If you don't intend to fix this in .el6, close it...

Yeah, not in 6, but certainly fixed in latest Fedora and 7.