[
https://issues.apache.org/jira/browse/HDFS-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776907#comment-13776907
]
Hadoop QA commented on HDFS-5217:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12603644/HDFS-5217.000.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
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 1.3.9) 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
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-HDFS-Build/5029//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5029//console
This message is automatically generated.
> Namenode log directory link is inaccessible in secure cluster
> -------------------------------------------------------------
>
> Key: HDFS-5217
> URL: https://issues.apache.org/jira/browse/HDFS-5217
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: HDFS-5217.000.patch
>
>
> Currently in a secured HDFS cluster, 401 error is returned when clicking the
> "NameNode Logs" link.
> Looks like the cause of the issue is that the httpServer does not correctly
> set the security handler and the user realm currently, which causes the
> httpRequest.getRemoteUser (for the log URL) to return null and later be
> overwritten to the default web name (e.g., "dr.who") by the filter. In the
> meanwhile, in a secured cluster the log URL requires the http user to be an
> administrator. That's why we see the 401 error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
