[
https://issues.apache.org/jira/browse/AMBARI-12197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin D Jetly updated AMBARI-12197:
------------------------------------
Description:
While adding a new service in kerberized cluster, we are using kerberos
descriptor persisted at cluster resource endpoint. This kerberos descriptor has
kerberos definition for all services present in the stack definition when
kerberos wizard was executed.
When a kerberos supporting uninstalled service and non-existing in a stack of
already kerberized cluster gets added later in the stack via HDP upgrade, Add
service wizard triggered subsequently after upgrade to install that service
will not show kerberos identities or configuration of that service for any user
customizations.
As part of this patch, new services properties are fetched from stack
descriptor instead of cluster descriptor. Also all the kerberos related
configuration (identities and properties) of a service in the stack descriptor
that are not present in the cluster descriptor are shown for customization and
applied to the cluster.
was:
While adding a new service in kerberized cluster, we are using kerberos
descriptor persisted at cluster resource endpoint. This kerberos descriptor has
kerberos definition for all services present in the stack definition when
kerberos wizard was executed.
When a kerberos supporting uninstalled service and non-existing in a stack of
already kerberized cluster gets added later in the stack via HDP upgrade, Add
service wizard triggered subsequently after upgrade to install that service
will not show kerberos identities or configuration of that service for any user
customizations.
As part of this patch, new services properties are fetched from stack
descriptor instead of cluster descriptor. Also all the kerberos realted
configuration (identities and properties) of a service in the stack descriptor
that are not present in the cluster descriptor are shown for customization and
applied to the cluster.
> Attempting to add service atlas does not show identities in kerberized cluster
> ------------------------------------------------------------------------------
>
> Key: AMBARI-12197
> URL: https://issues.apache.org/jira/browse/AMBARI-12197
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-12197.patch
>
>
> While adding a new service in kerberized cluster, we are using kerberos
> descriptor persisted at cluster resource endpoint. This kerberos descriptor
> has kerberos definition for all services present in the stack definition when
> kerberos wizard was executed.
> When a kerberos supporting uninstalled service and non-existing in a stack of
> already kerberized cluster gets added later in the stack via HDP upgrade, Add
> service wizard triggered subsequently after upgrade to install that service
> will not show kerberos identities or configuration of that service for any
> user customizations.
> As part of this patch, new services properties are fetched from stack
> descriptor instead of cluster descriptor. Also all the kerberos related
> configuration (identities and properties) of a service in the stack
> descriptor that are not present in the cluster descriptor are shown for
> customization and applied to the cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
