[AMBARI-19961] KERBEROS_CLIENT is not included automatically in all hostgroups when scaling a cluster after server restart

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.5.0
• Component/s: ambari-server
• Assignee: Magyari Sandor Szilard
• Reporter: Magyari Sandor Szilard
• Created: 10/Feb/17 15:08
• Updated: 14/Feb/17 11:05
• Resolved: 14/Feb/17 11:05

Description

When deploying a secure cluster TopologyManager automatically adds KERBEROS_CLIENT component to all hostgroups, so there's no need to add in Blueprint. Since hostgroups are part of Blueprint not Cluster template, which is not persisted during deploy after server restart KERBEROS_CLIENT is not present in hostgroups. This will affect scaling of a secure cluster after a server restart.

Issue Links

• links to: ReviewBoard