You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2015/09/15 00:24:47 UTC
[jira] [Commented] (AMBARI-9608) When adding the Oozie service to a
kerberized cluster OOZIE_SERVER doesn't start
[ https://issues.apache.org/jira/browse/AMBARI-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744405#comment-14744405 ]
Yusaku Sako commented on AMBARI-9608:
-------------------------------------
[~rlevas], are you sure? AMBARI-9966 is unresolved.
> 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)