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

Hadoop QA commented on AMBARI-9666:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12699604/AMBARI-9666_02.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 10 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-server.

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

This message is automatically generated.

> Kerberos: Adding a service to a Kerberized cluster requires Kerberos-related 
> tasks occur before INSTALL stage
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-9666
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9666
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Blocker
>              Labels: kerberos, kerberos_descriptor
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9666_01.patch, AMBARI-9666_02.patch
>
>   Original Estimate: 36h
>  Remaining Estimate: 36h
>
> When adding a service to a _Kerberized_ cluster, the {{INSTALL}} stage for 
> that service tends to fail due to missing Kerberos properties, principals and 
> keytabs. 
> To solve this issue, when a new service is added to a _Kerberized_ cluster 
> the following needs to occur before that service can attempt to transition 
> into it's {{INSTALLED}} state:
> # Kerberos-specific properties need to be created or set
> # Principals need to be created
> # Keytab files need to be generated
> # Keytab files need to be distributed 



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

Reply via email to