[jira] [Commented] (AMBARI-12782) Handle file permissions for jceks file in umask 027

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-12782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699790#comment-14699790 ] 

Hadoop QA commented on AMBARI-12782:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12750775/AMBARI-12782.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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/3595//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3595//console

This message is automatically generated.

> Handle file permissions for jceks file in umask 027
> ---------------------------------------------------
>
>                 Key: AMBARI-12782
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12782
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.1.1
>            Reporter: Gautam Borad
>            Assignee: Gautam Borad
>             Fix For: 2.1.2
>
>         Attachments: AMBARI-12782.patch
>
>
> # Handle : cd_access='a' for /etc/ranger/ (when jceks files are created)
> ** Audit to DB fails in a case if Ranger is not installed on same host as that of component host.
> ** For example Ranger is running on Host1 and Hiveserver2 is running on Host2. Then as /etc/ranger/<repository_name> gets created and has owner as hive user. However, due to umask setting /etc/ranger gets 750 permission with root:root as owner:group.
> ** Due to this when hive user tries to read the jceks file to generate audits to DB - it gets permission denied error.
> # rectifying ranger_audit_db passwd to be used while creating jceks for Ranger Audit DB



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)