[
https://issues.apache.org/jira/browse/AMBARI-18870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663704#comment-15663704
]
Hadoop QA commented on AMBARI-18870:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12838714/AMBARI-18870.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 4 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/9248//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9248//console
This message is automatically generated.
> Ranger PID file not being read if a custom location is provided
> ---------------------------------------------------------------
>
> Key: AMBARI-18870
> URL: https://issues.apache.org/jira/browse/AMBARI-18870
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0, 2.4.1, 2.4.2
> Reporter: Mugdha Varadkar
> Assignee: Mugdha Varadkar
> Fix For: 2.5.0
>
> Attachments: AMBARI-18870.patch
>
>
> Ranger PID file is not being read if a custom location is provided from
> Ambari.
> Fix include creation of .sh file which will have env variable with value as
> PID path. This .sh file will get executed by start script of service to make
> the env variable value to be taken into consideration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
