[
https://issues.apache.org/jira/browse/YARN-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542419#comment-13542419
]
Hadoop QA commented on YARN-288:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12562954/YARN-288.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 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:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServices
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/271//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/271//console
This message is automatically generated.
> Fair scheduler queue doesn't accept any jobs when ACLs are configured.
> ----------------------------------------------------------------------
>
> Key: YARN-288
> URL: https://issues.apache.org/jira/browse/YARN-288
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, scheduler
> Affects Versions: 2.0.2-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Fix For: 2.0.3-alpha
>
> Attachments: YARN-288.patch
>
>
> If a queue is configured with an ACL for who can submit jobs, no jobs are
> allowed, even if a user on the list tries.
> This is caused by using the scheduler thinking the user is "yarn", because it
> calls UserGroupInformation.getCurrentUser() instead of
> UserGroupInformation.createRemoteUser() with the given user name.
--
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
