[
https://issues.apache.org/jira/browse/AMBARI-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277352#comment-14277352
]
Rishi Pidva commented on AMBARI-8166:
-------------------------------------
[~jaimin], do you have a local KDC running on your machine? If yes, that would
explain it. The test which failed in your local environment makes an assumption
that nothing is listening on port 88 (stated in comments). We can change the
port to something which is typically not used by any service like 11111.
> 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,
> AMBARI-8166.patch.6, AMBARI-8166.patch.7, 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)
