[
https://issues.apache.org/jira/browse/AMBARI-19087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722646#comment-15722646
]
Hadoop QA commented on AMBARI-19087:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841764/AMBARI-19087.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 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/9523//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9523//console
This message is automatically generated.
> Clean up how dfs.cluster.administrators is handled wrt user/group creation
> --------------------------------------------------------------------------
>
> Key: AMBARI-19087
> URL: https://issues.apache.org/jira/browse/AMBARI-19087
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19087.patch
>
>
> dfs.cluster.administrators handles values of the following format:
>
>
> CL for the admins, this configuration is used to control who can access
> the default servlets in the namenode, etc. The value should be a comma
> separated list of users and groups. The user list comes first and is
> separated by a space followed by the group list, e.g. "user1,user2
> group1,group2". Both users and groups are optional, so "user1", " group1",
> "", "user1 group1", "user1,user2 group1,group2" are all valid (note the
> leading space in " group1"). '*' grants access to all users and groups, e.g.
> '*', '* ' and ' *' are all valid.
>
> Ambari cannot handle * value correctly it will try to create a group or user
> named '*'.
> Also Ambari cannot correctly create groups if there are multiple spaces
> instead of one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
