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

Hudson commented on AMBARI-19961:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #987 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/987/])
AMBARI-19961. KERBEROS_CLIENT is not included automatically in all (smagyari: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=771274a479f5d4f5c13f39ea723dc4de705337d7])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyManager.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/topology/TopologyManagerTest.java


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

Reply via email to