[
https://issues.apache.org/jira/browse/AMBARI-17301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336988#comment-15336988
]
Hadoop QA commented on AMBARI-17301:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811403/AMBARI-17301.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 2 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/7414//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7414//console
This message is automatically generated.
> Oozie service check will fail on non standard queue configuration
> -----------------------------------------------------------------
>
> Key: AMBARI-17301
> URL: https://issues.apache.org/jira/browse/AMBARI-17301
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Dmytro Grinenko
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17301.patch
>
>
> STR:
> Install Ambari
> change queue name from defualt
> run Oozie Service check
> problem is that we use examples from HDP provided sources, where queue name
> is hard-coded. We need found a way to run service check on existed queue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
