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

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-19961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862891#comment-15862891 ] 

Hadoop QA commented on AMBARI-19961:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12852257/AMBARI-19961.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/10532//console

This message is automatically generated.

> 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)