[jira] [Commented] (AMBARI-8166) Implement custom command for checking connectivity to KDC, via REST API

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

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

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/12690212/AMBARI-8166-v3.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Trunk compilation may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/1175//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, 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)