ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "rangerqa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RANGER-748) Users in policy got changed after upgrade
Date Tue, 01 Dec 2015 14:19:11 GMT

    [ https://issues.apache.org/jira/browse/RANGER-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033736#comment-15033736
] 

rangerqa commented on RANGER-748:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12774813/RANGER-748.patch
  against master revision 7a95ff0.

    {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}.  There were no new javadoc warning messages.

    +1 checkstyle.  The patch generated 0 code style errors.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
2.0.3) 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 .

Test results: https://builds.apache.org/job/PreCommit-RANGER-Build/12//testReport/
Console output: https://builds.apache.org/job/PreCommit-RANGER-Build/12//console

This message is automatically generated.

> Users in policy got changed after upgrade
> -----------------------------------------
>
>                 Key: RANGER-748
>                 URL: https://issues.apache.org/jira/browse/RANGER-748
>             Project: Ranger
>          Issue Type: Bug
>          Components: admin, usersync
>    Affects Versions: 0.5.1
>            Reporter: Gautam Borad
>            Assignee: Gautam Borad
>             Fix For: 0.5.1, 0.6.0
>
>         Attachments: RANGER-748.patch
>
>
> *Issue*
> After upgrading ranger from older version to latest : Users in x_user and x_portal_user
tables are not in sync and due to this policies populates wrong users after upgrade and service
check of plugin components fails. 
> *Root cause*
> As part of [commit | https://github.com/apache/incubator-ranger/commit/7c185e1f5a8881fd7a7ad0d60abd756b3cd416ec]
-   RangerPolicyRetriever.java [Line No: 253]. Code is to read username using userId. In this
function, userId being passed is of x_user table but code written is to read it from x_portal_user.
> So when IDs in x_user and x_portal_user are not in sync, this code will return wrong
username, and that's why username in policies will be changed with some other username.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message