[jira] [Commented] (AMBARI-10875) Kerberos Identity data is empty when Cluster.security_type != KERBEROS

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

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

Hadoop QA commented on AMBARI-10875:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12729680/AMBARI-10875_01.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:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/2595//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/2595//console

This message is automatically generated.

> Kerberos Identity data is empty when Cluster.security_type != KERBEROS
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-10875
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10875
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>              Labels: kerberos
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10875_01.patch
>
>
> Kerberos Identity data is empty when Cluster.security_type does not equal "KERBEROS".  
> Technically this seems to make sense since there shouldn't be any relevant Kerberos identities if the cluster isn't configured for Kerberos; however a _chicken-and-the-egg_ condition is encountered when manually enabled Kerberos and a listing of the needed Kerberos identities is needed before Kerberos is to be fully enabled. 
> *Solution*
> Allow the keberos_identities API end points to generate data even if Cluster.security_type is not equal to "KERBEROS".



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