[
https://issues.apache.org/jira/browse/AMBARI-14251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Magyari updated AMBARI-14251:
------------------------------------
Priority: Critical (was: Major)
> Blueprints: fix stale configs and kerberos-env stack defaults are not being
> applied during cluster deployment
> -------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-14251
> URL: https://issues.apache.org/jira/browse/AMBARI-14251
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Sandor Magyari
> Assignee: Sandor Magyari
> Priority: Critical
> Fix For: 2.2.0
>
>
> The following issues were discovered during Kerberized cluster deployment
> using Blueprints:
> 1. Stale configuration problem: Kerberos related configuration is generated
> for each host separately but applied on the whole Cluster. In case two
> components having common config types (like core-site in case of YARN_CLIENT
> and RESOURCEMANAGER) are deployed on two different hosts, Kerberos
> configuration changes generated by one host may interfere with config types
> deployed on other host. Eg. host2 modifies properties in core-site for
> RESOURCEMANAGER when same config type is already pushed to host1, causing
> Ambari to consider host1 with steal config.
> 2. Stack default values for properties in kerberos-env and krb5-conf are not
> being applied during cluster deployment in case they are defined only in
> Cluster create template configurations
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
