[
https://issues.apache.org/jira/browse/AMBARI-9666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-9666:
---------------------------------
Attachment: AMBARI-9666_01.patch
* Added code to inject Kerberos-related stages when added components move from
INIT to INSTALLED state
* Remove code that places stages in incorrect order in workflow
* Added ability to handle when hosts are removed, removing database entries for
principals on that host
* Changed when the auth_to_local map is built
* Handled adding hosts and adding services after Kerberos is enabled for the
cluster
Patch File [^AMBARI-9666_01.patch]
> 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
>
> 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 {{STARTED}} 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)
