[
https://issues.apache.org/jira/browse/AMBARI-12247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611494#comment-14611494
]
Hadoop QA commented on AMBARI-12247:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12743166/0001-AMBARI-12247-Use-separate-ranger-policymgr-ssl.xml-f.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/3332//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3332//console
This message is automatically generated.
> Ranger Plugin SSL configuration for YARN needs to be fixed to not clash with
> HDFS
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-12247
> URL: https://issues.apache.org/jira/browse/AMBARI-12247
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Velmurugan Periasamy
> Assignee: Velmurugan Periasamy
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments:
> 0001-AMBARI-12247-Use-separate-ranger-policymgr-ssl.xml-f.patch
>
>
> When enabling SSL for Ranger, Yarn plugin communication breaks due to the
> below two issues.
> 1] Ambari code generates ranger-policymgr-ssl.xml for both HDFS and Yarn.
> Need to generate different config file name for each service (because
> NameNode and ResourceManager can be running on the same host)
> 2] In yarn config (Advanced ranger-yarn-security),
> ranger.plugin.yarn.policy.rest.ssl.config.file attribute needs to be set as
> /etc/hadoop/conf/ranger-policymgr-ssl-yarn.xml => Currently, it is using the
> default value /etc/yarn/conf/ranger-policymgr-ssl.xml which is incorrect
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
