[
https://issues.apache.org/jira/browse/HADOOP-11175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164580#comment-14164580
]
Hadoop QA commented on HADOOP-11175:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12673800/HADOOP-11175.002.patch
against trunk revision 2a51494.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:red}-1 release audit{color}. The applied patch generated 1
release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/4886//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HADOOP-Build/4886//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/4886//console
This message is automatically generated.
> Fix several issues of hadoop security configuration in user doc.
> ----------------------------------------------------------------
>
> Key: HADOOP-11175
> URL: https://issues.apache.org/jira/browse/HADOOP-11175
> Project: Hadoop Common
> Issue Type: Bug
> Components: documentation, security
> Reporter: Yi Liu
> Assignee: Yi Liu
> Priority: Trivial
> Attachments: HADOOP-11175.002.patch, HDFS-7196.001.patch
>
>
> There are several issues of secure mode in user doc:
> {{dfs.namenode.secondary.keytab.file}} should be
> {{dfs.secondary.namenode.keytab.file}},
> {{dfs.namenode.secondary.kerberos.principal}} should be
> {{dfs.secondary.namenode.kerberos.principal}}.
> {{dfs.namenode.kerberos.https.principal}} doesn't exist, it should be
> {{dfs.namenode.kerberos.internal.spnego.principal}}.
> {{dfs.namenode.secondary.kerberos.https.principal}} doesn't exist, it should
> be {{dfs.secondary.namenode.kerberos.internal.spnego.principal}}.
> {{dfs.datanode.kerberos.https.principal}} doesn't exist, we can remove it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
