You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Sandor Magyari (JIRA)" <ji...@apache.org> on 2017/02/10 15:09:41 UTC

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

Sandor Magyari created AMBARI-19961:
---------------------------------------

             Summary: 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


When deploying a secure cluster TopologyManager automatically adds KERVEROS_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)