[
https://issues.apache.org/jira/browse/AMBARI-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261537#comment-14261537
]
jun aoki commented on AMBARI-8166:
----------------------------------
I have applied and quickly tested.
Found http://centos65-3:8080/api/v1/kdc_check/node1.mydomain.com
returns "UNREACHABLE" when no KDC is running
"REACHABLE" after following commands
{code}
yum install krb5-server krb5-libs krb5-auth-dialog krb5-workstation
kdb5_util create
service krb5kdc start
{code}
This looks good to me
+1
I can commit it unless [~jaimin] , [~rlevas], and [~rpidva] have anything to
say.
> 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.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)
