[
https://issues.apache.org/jira/browse/AMBARI-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256827#comment-14256827
]
Hadoop QA commented on AMBARI-8166:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12688819/AMBARI-8166.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-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1066//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1066//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.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)
