[
https://issues.apache.org/jira/browse/AMBARI-12233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610667#comment-14610667
]
Hadoop QA commented on AMBARI-12233:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12743091/AMBARI-12233.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:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3328//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3328//console
This message is automatically generated.
> Custom actions do not allow max time out higher than 10 minutes
> ---------------------------------------------------------------
>
> Key: AMBARI-12233
> URL: https://issues.apache.org/jira/browse/AMBARI-12233
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-12233.patch
>
>
> Custom action cannot have a timeout more than 10 minutes. This is not in line
> with configurable task time outs that are by default 15 minutes for all tasks
> and 30 minutes for install tasks.
> Custom action definition should be allowed to provide arbitrary timeout
> values. The task timeout provided at ambari.properties {{agent.task.timeout}}
> will override the timeout specified for custom actions if it is larger.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
