[
https://issues.apache.org/jira/browse/AMBARI-11676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14572182#comment-14572182
]
Hudson commented on AMBARI-11676:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2806 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2806/])
AMBARI-11676. dfs.encryption.key.provider.uri is not set in unsecure cluster
with ranger kms enabled (srimanth) (sgunturi:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=705c35a8b3c701fe0c6a50ce053239110f84dd5b)
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
> dfs.encryption.key.provider.uri is not set in unsecure cluster with ranger
> kms enabled
> --------------------------------------------------------------------------------------
>
> Key: AMBARI-11676
> URL: https://issues.apache.org/jira/browse/AMBARI-11676
> Project: Ambari
> Issue Type: Bug
> Components: contrib
> Affects Versions: 2.1.0
> Reporter: Srimanth Gunturi
> Assignee: Srimanth Gunturi
> Fix For: 2.1.0
>
> Attachments: AMBARI-11676.patch
>
>
> On a unsecure cluster with Ranger + Ranger KMS + TDE, I noticed that
> dfs.encryption.key.provider.uri in hdfs-site.xml was not set.
> core-site.xml
> <property>
> <name>hadoop.security.key.provider.path</name>
> <value>kms://[email protected]:9292/kms</value>
> </property>
> hdfs-site.xml
> <property>
> <name>dfs.encryption.key.provider.uri</name>
> <value></value>
> </property>
> Ambari UI showed the correct configs for both core-site.xml and hdfs-site.xml
> but on the cluster, the value in hdfs-site.xml was missing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
