[
https://issues.apache.org/jira/browse/AMBARI-17399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346320#comment-15346320
]
Hadoop QA commented on AMBARI-17399:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12812803/AMBARI-17399.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 1 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-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7506//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7506//console
This message is automatically generated.
> Hive llap principals are shown on Configure Identity even when Hive is not
> deployed
> -----------------------------------------------------------------------------------
>
> Key: AMBARI-17399
> URL: https://issues.apache.org/jira/browse/AMBARI-17399
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17399.patch,
> hive_llap_principal_and_Keytab_present_unconditionally.png
>
>
> 1. Deploy ambari cluster with YARN, HDFS, ZOOKEEPER and HBASE
> 2. enable security (AD)
> Expected: On ConfigureIdentities page hive.llap.zk.sm.principal and
> hive.llap.zk.sm.keytab.file
> should not be present if hive is not deployed on cluster.
> Actual: These 2 properties are showing under Ambari Principals panel even
> when Hive is not deployed on the cluster.
> Attached screenshot for reference.
> *Cause*
> This is caused when identities that have _when_ clauses are not filtered out
> if the when clause evaluates to {{false}} when the UI queries for the
> (composite) Kerberos Descriptor.
> *Solution*
> Use the {{evaluate_when}} and (optionally) the {{additional_services}}
> _{{GET}} directives_ to have {{when}} Kerberos descriptor identitiy {{when}}
> clauses evaluated when requesting Kerberos descriptors.
> {noformat:title=Get composite Kerberos descriptor when enabling Kerberos}
> GET
> /api/v1/clusters/CLUSTER_NAME/kerberos_descriptors/COMPOSITE?evaluate_when=true
> {noformat}
> {noformat:title=Get composite Kerberos descriptor when adding services (HIVE,
> PIG, and TEZ)}
> GET
> /api/v1/clusters/CLUSTER_NAME/kerberos_descriptors/COMPOSITE?evaluate_when=true&additional_services=HIVE,TEZ,PIG
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
