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

Hadoop QA commented on AMBARI-18377:
------------------------------------

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

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8652//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8652//console

This message is automatically generated.

> Retry Installing Kerberos Clients skips hosts were it failed (if lost 
> heartbeat)
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-18377
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18377
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.4.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-18377.patch
>
>
> STR:
> * Installed Ambari 2.4 with HDP 2.5
> * Attempted to Kerberize the cluster and looks like one of the agents lost 
> heartbeat
> * The UI showed a "Retry" button, but it completely ignored the host were it 
> lost the heartbeat on
> This means that Kerberos Client did not install on that host and the Wizard 
> proceeded to the next step. Therefore, starting services on that host failed.
> ambari-server-2.4.0.0-1010.x86_64
> ambari-server --hash
> c32861b10d438dea03227d4bf737600f4a7040c9



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to