[
https://issues.apache.org/jira/browse/AMBARI-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134677#comment-15134677
]
Hadoop QA commented on AMBARI-14938:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12786501/AMBARI-14938_trunk_01.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 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/5233//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5233//console
This message is automatically generated.
> Some user-specified auth-to-local rules fail to render when auto generating
> auth-to-local rules
> -----------------------------------------------------------------------------------------------
>
> Key: AMBARI-14938
> URL: https://issues.apache.org/jira/browse/AMBARI-14938
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Labels: kerberos
> Fix For: 2.2.2
>
> Attachments: AMBARI-14938_branch-2.2_01.patch,
> AMBARI-14938_trunk_01.patch
>
>
> When processing the user-specified auth-to-local rules while automatically
> generating auth-to-local rule sets using
> {{org.apache.ambari.server.controller.AuthToLocalBuilder}}, some rules fail
> to render.
> This occurs when escape characters are used in the replacement pattern or
> replacement string of the rule, where a role looks like:
> {code}
> RULE: [n:string](regexp)s/pattern/replacement/[g]
> {code}
> To fix this issue, the regular expression used to parse the rules need to be
> augmented to allow for those characters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)