[ 
https://issues.apache.org/jira/browse/AMBARI-21117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023896#comment-16023896
 ] 

Hadoop QA commented on AMBARI-21117:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12869740/AMBARI-21117.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 2 new 
or modified test files.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11611//console

This message is automatically generated.

> Existing hosts state didn't save after host was added
> -----------------------------------------------------
>
>                 Key: AMBARI-21117
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21117
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.5.1
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>             Fix For: 2.5.2
>
>         Attachments: AMBARI-21117.patch
>
>
> Existing hosts state didn't save after host was added. In next test add host 
> wizard stay open.
> When we connect to cluster - automatically redirect on add host wizard. 
> (attached screenshot)
> First step validation passed and host registered successfully. 
> On Review Page, when we clicked Deploy we had popup with error that this host 
> already part of cluster.
> If we cluster wizard and try it again - validation on first step not passed



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to