Sandor Molnar created AMBARI-23526:
--------------------------------------

             Summary: Missing unlimited JCE policy installation on ambari-agent 
side
                 Key: AMBARI-23526
                 URL: https://issues.apache.org/jira/browse/AMBARI-23526
             Project: Ambari
          Issue Type: Bug
          Components: ambari-agent, ambari-server
    Affects Versions: 2.7.0
            Reporter: Sandor Molnar
            Assignee: Sandor Molnar
             Fix For: 2.7.0


*STR:*
1. install Ambari 2.7.0.0 (build #220) server/agents on Centos7 machines (this 
issue is not OS dependent)
2. install an HDP 3.0 cluster with HDFS
3. check if unlimited JCE policy has been installed on the hosts where only 
ambari-agent has been installed:
{code}
[root@c7402 ~]# /usr/jdk64/jdk1.8.0_112/bin/java -jar 
/var/lib/ambari-agent/tools/jcepolicyinfo.jar -tu
{code}
*Result:*
{code}
[root@c7402 ~]# /usr/jdk64/jdk1.8.0_112/bin/java -jar 
/var/lib/ambari-agent/tools/jcepolicyinfo.jar -tu
Unlimited Key JCE Policy: false
{code}
*Expected result:*
{code}
[root@c7402 ~]# /usr/jdk64/jdk1.8.0_112/bin/java -jar 
/var/lib/ambari-agent/tools/jcepolicyinfo.jar -tu
Unlimited Key JCE Policy: true
{code}
*Additional information:*
unlimited JCE policy in agent side is triggered by a hook: 
ambari-server/src/main/resources/stack-hooks/before-START/scripts/hook.py:38 -> 
ambari-server/src/main/resources/stack-hooks/before-START/scripts/shared_initialization.py

In this Python code we check if we really need to install unlimited JCE:
{code}
  elif not params.unlimited_key_jce_required:
    Logger.debug("Skipping unlimited key JCE policy check and setup since it is 
not required")
{code}
This parameter is being set in params_linux.py:
{code}
unlimited_key_jce_required = 
default("/componentLevelParams/unlimited_key_jce_required", False)
{code}
However 
org/apache/ambari/server/controller/AmbariManagementControllerImpl.java:2590 
sets it in the host level parameters (and not in component level params)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to