[
https://issues.apache.org/jira/browse/AMBARI-15594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213746#comment-15213746
]
Hadoop QA commented on AMBARI-15594:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12795515/AMBARI-15954.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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6050//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6050//console
This message is automatically generated.
> Enabling logging of commands breaks execution commands
> ------------------------------------------------------
>
> Key: AMBARI-15594
> URL: https://issues.apache.org/jira/browse/AMBARI-15594
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.2.2
> Reporter: Sandor Magyari
> Assignee: Sandor Magyari
> Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15954.patch
>
>
> After enabling logging of command results, RESTART/START commands hangs.
> Config modified based on: https://issues.apache.org/jira/browse/AMBARI-15393
> Error in the log:
> {code}
> WARNING 2016-03-25 23:40:47,808 ActionQueue.py:211 - cannot concatenate 'str'
> and 'int' objects
> {code}
> Seems to be due to {code}
> "Begin command output log for command with id = " + command['taskId']
> {code} where the second one is an int. Not sure if its due to python version
> but it reproduces on centos6 vagrant VMs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
