[
https://issues.apache.org/jira/browse/AMBARI-15051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148482#comment-15148482
]
Hadoop QA commented on AMBARI-15051:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12787982/AMBARI-15051.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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.checks.CheckDatabaseHelperTest
org.apache.ambari.server.stack.StackManagerTest
org.apache.ambari.server.stack.KerberosDescriptorTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5381//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5381//console
This message is automatically generated.
> Improvements and fixes for database check
> -----------------------------------------
>
> Key: AMBARI-15051
> URL: https://issues.apache.org/jira/browse/AMBARI-15051
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.2.2
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15051.patch
>
>
> – Log outputs to a separate file (this is already an ask from SmartSense)
> – Use ERROR/WARNING/INFO to mark logs that fit the level
> – Either the python script or the system test validation code can parse the
> log file for ERROR and WARNING logs and post a summary - as Sunitha Velpula
> suggested.
> – Take in account fact that clusters count could be more then one in service
> config check
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
