You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Qiang Zhang (JIRA)" <ji...@apache.org> on 2017/04/18 04:51:41 UTC
[jira] [Resolved] (RANGER-1515) Run updatepolicymgrpassword.sh and
updatepolicymgrpassword.py to update policy mgr password failed.
[ https://issues.apache.org/jira/browse/RANGER-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Qiang Zhang resolved RANGER-1515.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
> Run updatepolicymgrpassword.sh and updatepolicymgrpassword.py to update policy mgr password failed.
> ---------------------------------------------------------------------------------------------------
>
> Key: RANGER-1515
> URL: https://issues.apache.org/jira/browse/RANGER-1515
> Project: Ranger
> Issue Type: Bug
> Components: usersync
> Affects Versions: 1.0.0
> Reporter: peng.jianhua
> Assignee: peng.jianhua
> Labels: patch
> Fix For: 1.0.0
>
> Attachments: 0001-RANGER-1515-Run-updatepolicymgrpassword.sh-and-updat.patch
>
>
> The "chown: invalid user: ‘ranger:ranger’" would appear when run updatepolicymgrpassword.sh and updatepolicymgrpassword.py to update policy mgr password. Test steps is following:
> 1. Using following configuration to install the Ranger UserSync Process in install.properties.
> unix_user=usersync
> unix_group=usersync
> 2. Running updatepolicymgrpassword.sh. or updatepolicymgrpassword.py to update policy mgr password.
> The linux user processing logic of the installer for the Ranger UserSync Process, updatepolicymgrpassword.sh and updatepolicymgrpassword.py is inconsistent. The installer for the Ranger UserSync Process use configuration parameters to create linux user. However updatepolicymgrpassword.sh and updatepolicymgrpassword.py use hard code get linux user. In above test steps the usersync user and usersync group was created when installing the Ranger UserSync Process. ranger user and ranger group don't exist. In chown ${unix_user}:${unix_group} `dirname "${SYNC_LDAP_BIND_KEYSTOREPATH}"` the updatepolicymgrpassword.sh used ranger user and ranger group. The updatepolicymgrpassword.sh code is as following:
> unix_user=ranger
> unix_group=ranger
> chown ${unix_user}:${unix_group} `dirname "${SYNC_LDAP_BIND_KEYSTOREPATH}"`.
> The installer for the Ranger UserSync Process code is as following:
> unix_user = globalDict['unix_user']
> ownerName = mergeProps[unixUserProp]
> groupName = mergeProps[unixGroupProp]
> ownerId = createUser(ownerName, groupName)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)