[
https://issues.apache.org/jira/browse/AMBARI-8235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14203806#comment-14203806
]
Hadoop QA commented on AMBARI-8235:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12680467/AMBARI-8235.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/573//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/573//console
This message is automatically generated.
> 'Retry' on start all services in security wizard does not show progress
> -----------------------------------------------------------------------
>
> Key: AMBARI-8235
> URL: https://issues.apache.org/jira/browse/AMBARI-8235
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 1.5.1
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8235.patch, AMBARI-8235_branch-1.7.0.patch,
> Screen Shot 2014-11-08 at 9.49.45 PM.png
>
>
> *STR:*
> # Go to security wizard ->Deploy step
> # Let Start Services command fail
> # Click on Start Services link. Go to Hosts->Tasks->Task Details (stdout and
> stderr) page for any task
> # Click on OK on task details page of the host_propgress_popup and get back
> to Deploy page of security wizard.
> # Click on Retry button.
> *Reason:*
> There is a code that updates the current task details page. This considers
> last seen task as the current task for doing dynamic update for the stdout
> and stderr information. Details of the last seen task keeps on updating on
> polling interval (or hitting retry) irrespective of it is still open or not.
> On the mentioned STR this code causes JS error because it tries to update the
> task details by finding it in the current request which when retried does not
> exist.
> *Solution:*
> Skip updating the current task details if the current taskId (last seen task)
> is not found in the current request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
