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

Hadoop QA commented on AMBARI-13211:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12764466/AMBARI-13211.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 1 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-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/3883//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/3883//console

This message is automatically generated.

> Host checks does not report all errors in first check
> -----------------------------------------------------
>
>                 Key: AMBARI-13211
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13211
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Di Li
>            Assignee: Di Li
>            Priority: Minor
>             Fix For: trunk
>
>         Attachments: AMBARI-13211.patch
>
>
> For a cluster with existing folders such as /etc/oozie,on the cluster install 
> wizard, the first run of the host check after registering the Ambari agent 
> may not show any warnings about existing folders. If user reruns the checks, 
> the UI then shows warnings about existing folders in the cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to