You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2013/07/05 17:37:48 UTC
[jira] [Updated] (AMBARI-2578) Using another user for ambari server
user create a local group for the ambari server user with same name.
[ https://issues.apache.org/jira/browse/AMBARI-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitry Lysnichenko updated AMBARI-2578:
---------------------------------------
Component/s: controller
Affects Version/s: 1.2.5
Fix Version/s: 1.2.5
Assignee: Dmitry Lysnichenko
> Using another user for ambari server user create a local group for the ambari server user with same name.
> ---------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-2578
> URL: https://issues.apache.org/jira/browse/AMBARI-2578
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.2.5
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 1.2.5
>
>
> Using an ambari-qa user (that is a ldap user and he has hadoop set up as a primary ldap group)
> {code}
> [root@va21 ldap]# id ambari-qa
> uid=524(ambari-qa) gid=522(hadoop) groups=522(hadoop)
> {code}
> causes ambari-server setup to create an ambari-qa local group (at /etc/group).
> {code}
> ambari-qa:x:601:ambari-qa
> [root@va21 ldap]# id ambari-qa
> uid=524(ambari-qa) gid=522(hadoop) groups=522(hadoop),601(ambari-qa)
> {code}
> Ldap users and groups are transparent for ambari-server, it starts well.
> The problem is that additional group is created.
--
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