[
https://issues.apache.org/jira/browse/AMBARI-20047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874769#comment-15874769
]
Hadoop QA commented on AMBARI-20047:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12853570/AMBARI-20047.1.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
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10654//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10654//console
This message is automatically generated.
> Repository config user needs to set customized service user in Ranger when
> service plugin is enabled
> ----------------------------------------------------------------------------------------------------
>
> Key: AMBARI-20047
> URL: https://issues.apache.org/jira/browse/AMBARI-20047
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.0
> Reporter: Vishal Suvagia
> Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-20047.1.patch, AMBARI-20047.patch
>
>
> The property {{REPOSITORY_CONFIG_USERNAME}} in Advanced
> ranger-*-plugin-properties is not updated to the custom user-name when
> services are using custom users.
> This causes issues especially in cases of Test connection, and policy user
> which is given default permissions in Ranger.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
