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.

1. fire up Add Existing Cluster dialog
2. fill in details for one node
3. click Connect twice in a short period of time (before the response
   for the first AJAX request comes back)

BAD:

Respective nodes listed twice.

GOOD:

Respective nodes listed just once, no matter how many clicks there were.

Note: there may be more situations like this.

Should be easy enough to fix by disabling the submit button while we're waiting for the response.

commit 72fa237fc759c83c927d87bad5ee8d51dab3c0db
Author: Ryan McCabe <rmccabe>
Date:   Mon Oct 8 09:55:18 2012 -0400

    luci: Fix double click on add existing dialog
    
    Fix a bug that caused nodes to be listed twice if you accidentally
    double clicked the "Connect" button on the add existing cluster
    dialog.
    
    Resolves: rhbz#856253
    
    Signed-off-by: Ryan McCabe <rmccabe>

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.

http://rhn.redhat.com/errata/RHBA-2013-0309.html