[
https://issues.apache.org/jira/browse/AMBARI-17772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-17772:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 9db1834941ee24cb7c23fc8254f023aa51433a96
Author: Robert Levas <[email protected]>
Date: Tue Jul 19 10:21:30 2016 -0400
{noformat}
Committed to branch-2.4
{noformat}
commit 44719444660a87e0f692749e8e626bdeb61c10eb
Author: Robert Levas <[email protected]>
Date: Tue Jul 19 11:52:35 2016 -0400
{noformat}
> Kerberos-related configs are not applied before INSTALL command is built on
> add service
> ---------------------------------------------------------------------------------------
>
> Key: AMBARI-17772
> URL: https://issues.apache.org/jira/browse/AMBARI-17772
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Priority: Critical
> Labels: kerberos, regression
> Fix For: 2.4.0
>
> Attachments: AMBARI-17772_branch-2.4_01.patch,
> AMBARI-17772_branch-2.4_02.patch, AMBARI-17772_trunk_01.patch,
> AMBARI-17772_trunk_02.patch
>
>
> Kerberos-related configs are not applied before INSTALL command is built on
> add service.
> This occurs when new services and components are added to an existing cluster
> where Kerberos is enabled. Due to the order of when command detail (JSON)
> structures are built and when service configurations are set,
> Kerberos-related configurations will not be available for new services. This
> is a regression created by the patch for AMBARI-17629.
> *Solution*
> Ensure that Kerberos-related configuration updates are applied before the
> INSTALL command details are created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
