[
https://issues.apache.org/jira/browse/HADOOP-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13218424#comment-13218424
]
Hadoop QA commented on HADOOP-8098:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12516360/HADOOP-8098.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/637//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/637//console
This message is automatically generated.
> KerberosAuthenticatorHandler should use _HOST replacement to resolve
> principal name
> -----------------------------------------------------------------------------------
>
> Key: HADOOP-8098
> URL: https://issues.apache.org/jira/browse/HADOOP-8098
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 0.24.0, 0.23.2
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Fix For: 0.23.2
>
> Attachments: HADOOP-8098.patch
>
>
> Currently the exact Kerberos principal name has to be set in the
> configuration of each node.
> KerberosAuthenticatorHandler should do similar logic as the RPC ports to
> support HTTP/_HOST@REALM
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
