[AMBARI-14251] Blueprints: fix stale configs and kerberos-env stack defaults are not being applied during cluster deployment

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.2.0
• Component/s: ambari-server
• Assignee: Magyari Sandor Szilard
• Reporter: Magyari Sandor Szilard
• Due: 08/Dec/15
• Created: 07/Dec/15 16:37
• Updated: 09/Dec/15 04:29
• Resolved: 08/Dec/15 22:52

Description

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