[
https://issues.apache.org/jira/browse/AMBARI-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659074#comment-14659074
]
Hadoop QA commented on AMBARI-12652:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12748895/AMBARI-12652.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
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3534//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3534//console
This message is automatically generated.
> Repeated debug log during Blueprint deployment should not be present by
> default
> -------------------------------------------------------------------------------
>
> Key: AMBARI-12652
> URL: https://issues.apache.org/jira/browse/AMBARI-12652
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.1
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Fix For: 2.1.1
>
> Attachments: AMBARI-12652.patch
>
>
> During a Blueprint deployment, the following log message appears repeatedly:
> {code}
> ExecutionCommandWrapper:109 - ExecutionCommandWrapper.getExecutionCommand:
> refreshConfigTag set to *, so clearing config for full refresh.
> {code}
> This log message is useful for debugging deployment failures in large
> clusters, but should not be present in the log by default, as this message
> repeats often enough to make debugging normal conditions less simple.
> This log message is currently logged at the INFO level, but should be changed
> to log at the DEBUG level.
> I'm working on a fix for this, and will be submitting a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
