[
https://issues.apache.org/jira/browse/AMBARI-9324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291947#comment-14291947
]
Hadoop QA commented on AMBARI-9324:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12694555/AMBARI-9324_01.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/1487//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1487//console
This message is automatically generated.
> Kerberos: when unable to connect to KDC admin, need to inform user
> ------------------------------------------------------------------
>
> Key: AMBARI-9324
> URL: https://issues.apache.org/jira/browse/AMBARI-9324
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Labels: kerberos
> Fix For: 2.0.0
>
> Attachments: AMBARI-9324_01.patch
>
>
> This appears to be happening when the KDC and/or KDC Admin hosts do not point
> to a valid KDC, and when the relevant KDC does not _handle_ the indicated
> realm.
> For the *host* issue, (in the cases that I tested), a
> {{org.apache.ambari.server.serveraction.kerberos.KerberosKDCConnectionException}}
> is being thrown but not caught to re-throw a
> {{java.lang.IllegalArgumentException}}, which would generate the expected 400
> error.
> For the *realm* issue, the following error string is not being captured by
> the logic to produce a
> {{org.apache.ambari.server.serveraction.kerberos.KerberosRealmException}}.
> {code}
> kadmin: Cannot find KDC for requested realm while initializing kadmin
> interface
> {code}
> In any case,
> {{org.apache.ambari.server.serveraction.kerberos.KerberosRealmException}} is
> not being caught to re-throw a {{java.lang.IllegalArgumentException}}, which
> would generate the expected 400 error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
