[
https://issues.apache.org/jira/browse/AMBARI-19961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Magyari updated AMBARI-19961:
------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> KERBEROS_CLIENT is not included automatically in all hostgroups when scaling
> a cluster after server restart
> -----------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-19961
> URL: https://issues.apache.org/jira/browse/AMBARI-19961
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Sandor Magyari
> Assignee: Sandor Magyari
> Fix For: 2.5.0
>
> Attachments: AMBARI-19961.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
