Bug 856253

Summary:	Double click on "connect" in Add Existing Cluster dialog leads to listing the nodes twice
Product:	Red Hat Enterprise Linux 6	Reporter:	Jan Pokorný [poki] <jpokorny>
Component:	luci	Assignee:	Ryan McCabe <rmccabe>
Status:	CLOSED ERRATA	QA Contact:	Cluster QE <mspqa-list>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.3	CC:	cluster-maint, djansa, rsteiger
Target Milestone:	rc	Keywords:	EasyFix
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	luci-0.26.0-16.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-21 08:22:32 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 Jan Pokorný [poki] 2012-09-11 14:56:30 UTC

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.

Comment 1 Jan Pokorný [poki] 2012-09-11 14:59:07 UTC

Note: there may be more situations like this.

Comment 2 Ryan McCabe 2012-09-28 15:12:25 UTC

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

Comment 3 Ryan McCabe 2012-10-08 13:58:09 UTC

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>

Comment 7 errata-xmlrpc 2013-02-21 08:22:32 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.

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