[
https://issues.apache.org/jira/browse/AMBARI-17301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341802#comment-15341802
]
Hudson commented on AMBARI-17301:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #5121 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5121/])
AMBARI-17301. Oozie service check will fail on non standard queue (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6c2a175198af7f8d25e695e9d036fde88549ee43])
*
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/service_check.py
* ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_service_check.py
*
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/files/prepareOozieHdfsDirectories.sh
*
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py
* ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_service_check.py
> 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
> Assignee: Andrew Onischuk
> 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)
