[
https://issues.apache.org/jira/browse/AMBARI-13177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904356#comment-14904356
]
Hadoop QA commented on AMBARI-13177:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12761834/AMBARI-13177.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/3837//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3837//console
This message is automatically generated.
> For HDP 2.2: Ranger setup does not respect custom service users
> ---------------------------------------------------------------
>
> Key: AMBARI-13177
> URL: https://issues.apache.org/jira/browse/AMBARI-13177
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Gautam Borad
> Assignee: Gautam Borad
> Fix For: 2.1.3
>
> Attachments: AMBARI-13177.patch
>
>
> PROBLEM: In an Ambari install it's possible to use different user accounts
> for service users, such as the hive user and the hdfs user.
> The plugin enable scripts set the owner of various component specific files
> such as the jceks files. When the services use custom users, the ranger
> scripts still set the owner of the files to the "standard user", resulting in
> permissions problems.
> For example if I make my hive user "special-hive-user", the ranger scripts
> still will set the owner to "hive".
> The ranger scripts need to use the information in Ambari for the custom
> service users and propagate this to the setup scripts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
