[
https://issues.apache.org/jira/browse/AMBARI-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14260243#comment-14260243
]
Hudson commented on AMBARI-8940:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #1354 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1354/])
AMBARI-8940. Ambari overrides user/groups settings configured by cluster admins
(aonishuk) (aonishuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dc097d18d458bcdaab7de77af3f2ccffe81e86b1)
* contrib/fast-hdfs-resource/dependency-reduced-pom.xml
* ambari-common/src/main/python/resource_management/core/providers/system.py
* ambari-common/src/main/python/resource_management/core/providers/accounts.py
*
ambari-common/src/main/python/resource_management/libraries/functions/get_namenode_states.py
* ambari-common/src/main/python/resource_management/core/resources/accounts.py
> Ambari overrides user/groups settings configured by cluster admins
> ------------------------------------------------------------------
>
> Key: AMBARI-8940
> URL: https://issues.apache.org/jira/browse/AMBARI-8940
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.1.0
>
>
> Seen at Altiscale who were trying to use YARN with docker on an Ambari
> deployed cluster.
> Docker requires users to be in the "docker" group to be able to launch docker
> containers. As a result, the user "yarn", which Ambari creates and adds to the
> "hadoop" group, was changed to belong to both the "docker" and "hadoop"
> groups.
> However, after making this change on all nodes, we noticed that the the yarn
> user was being removed from the docker group.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
