Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 14 Jan 2015 04:13:34 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12753131.1415214097000.78116.1421208814461@Atlassian.JIRA>
In-Reply-To: <JIRA.12753131.1415214097000@Atlassian.JIRA>
References: <JIRA.12753131.1415214097000@Atlassian.JIRA>
 <JIRA.12753131.1415214097912@arcas>
Subject: [jira] [Commented] (AMBARI-8166) Implement custom command for
 checking connectivity to KDC, via REST API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hadoop QA commented on AMBARI-8166:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12692124/AMBARI-8166.patch.5
  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:red}-1 core tests{color}.  The patch failed these unit tests in ambari-server:

                  org.apache.ambari.server.api.rest.KdcServerConnectionVerificationTest

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

This message is automatically generated.

> Implement custom command for checking connectivity to KDC, via REST API
> -----------------------------------------------------------------------
>
>                 Key: AMBARI-8166
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8166
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-agent, ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>            Assignee: Rishi Pidva
>              Labels: connectivity_, kdc, kerberos
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8166-v2.patch, AMBARI-8166-v3.patch, AMBARI-8166.patch, AMBARI-8166.patch.4, AMBARI-8166.patch.5, Screen Shot 2014-11-04 at 11.16.41 PM.png
>
>
> There needs to be a way, given the details about a KDC to verify that Ambari and (optionally) the nodes in the existing cluster can connect to it. 
> From the cluster hosts, this test should test that the address and port combinations are reachable. 
> From the Ambari server, this test should make sure the administrator credentials allow at least read access to the KDC.
> As an example of a similar action, see how Oozie does this for DB check pre install.


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