[
https://issues.apache.org/jira/browse/AMBARI-14574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102404#comment-15102404
]
Hadoop QA commented on AMBARI-14574:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12782546/AMBARI-14574.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 5 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/4943//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4943//console
This message is automatically generated.
> multiple clicks on "Next" button causes skipping of steps while installing a
> cluster
> ------------------------------------------------------------------------------------
>
> Key: AMBARI-14574
> URL: https://issues.apache.org/jira/browse/AMBARI-14574
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.1
> Reporter: Keta Patel
> Assignee: Keta Patel
> Attachments: AMBARI-14574.patch
>
>
> On installation wizard, multiple clicks on the "Next" button can cause
> skipping of steps. The timing of the 2nd click decides if that click will be
> processed again or not. The following JIRAs had the same issue:
> AMBARI-7195
> AMBARI-7315
> The fix for the above issues helps to resolve most part of the problem. But
> if the user happened to click again at the point when the last callback
> function has just completed (and thus, has made the "Next" button clickable
> again) but the next step has not yet completed its rendering, then the 2nd
> click gets processed again. The "current step" was already updated in the
> code to point to the next step, from the 1st click. So when this 2nd click
> calls the "next" function in the router, the subsequent step of the "current
> step" gets set as the current step. As a result we skip steps.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
