[
https://issues.apache.org/jira/browse/AMBARI-16006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251762#comment-15251762
]
Hadoop QA commented on AMBARI-16006:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12799942/AMBARI-16006.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/6577//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6577//console
This message is automatically generated.
> Add logging to check_host.py
> ----------------------------
>
> Key: AMBARI-16006
> URL: https://issues.apache.org/jira/browse/AMBARI-16006
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-16006.patch
>
>
> Sometimes host check after host registration lasted too long (more than 720
> sec.). I's affect some system tests. I can't reproduce this, so it would be
> good to add logging to this operation.
> Currently, all the host check logs available are
>
>
>
> [root@c6404 data]# cat /var/lib/ambari-agent/data/output-3.txt
> Last Agent Env check started.
> Last Agent Env check completed successfully.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
