Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 14 Sep 2015 23:12:46 +0000 (UTC)
From: "Robert Levas (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12774667.1423769037000.336407.1442272366136@Atlassian.JIRA>
In-Reply-To: <JIRA.12774667.1423769037000@Atlassian.JIRA>
References: <JIRA.12774667.1423769037000@Atlassian.JIRA>
 <JIRA.12774667.1423769037592@arcas>
Subject: [jira] [Commented] (AMBARI-9608) When adding the Oozie service to a
 kerberized cluster OOZIE_SERVER doesn't start
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Levas commented on AMBARI-9608:
--------------------------------------

[~u39kun], Sorry about that.  My previous comment should have read:  

Fixed with the resolution of AMBARI-9666.


> When adding the Oozie service to a kerberized cluster OOZIE_SERVER doesn't start
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-9608
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9608
>             Project: Ambari
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 2.0.0
>            Reporter: John Speidel
>            Priority: Critical
>              Labels: keberos
>             Fix For: 2.0.0
>
>
> Oozie server fails to start with the error: "Fail: Configuration parameter 'oozie.service.HadoopAccessorService.kerberos.principal' was not found in configurations dictionary!"
> Steps to reproduce:
> Create a non-kerberized cluster
> I used the following blueprint
> {code}
> {   
>   "host_groups" : [
>     {
>       "name" : "host_group_1",
>       "components" : [      
>         {
>           "name" : "NODEMANAGER"
>         },
>         {
>           "name" : "NAMENODE"
>         },
>         {
>           "name" : "HISTORYSERVER"
>         },
>         {
>           "name" : "ZOOKEEPER_SERVER"
>         },
>         {
>           "name" : "SECONDARY_NAMENODE"
>         },
>         {
>           "name" : "RESOURCEMANAGER"
>         },  
>         {
>           "name" : "APP_TIMELINE_SERVER"
>         },        
>         {
>           "name" : "DATANODE"
>         },
>         {
>           "name" : "YARN_CLIENT"
>         },
>         {
>           "name" : "ZOOKEEPER_CLIENT"
>         },
>         {
>           "name" : "MAPREDUCE2_CLIENT"
>         }     
>       ],
>       "cardinality" : "1"
>     }
>   ],
>   "Blueprints" : {
>     "stack_name" : "HDP",
>     "stack_version" : "2.2"
>   }
> }
> {code}
> - manually unzip UnlimitedJCEPolicy
> - manually install MIT KDC
> - Using UI, kerberize the existing cluster
> - Using the UI, add the Oozie service
> OOZIE_SERVER failed to start and the above noted exception was from the log that is exposed via the UI for the oozie start operation.
> According to Robert Levas this property is in the kerberos descriptor it should be set.


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