[
https://issues.apache.org/jira/browse/AMBARI-20034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883280#comment-15883280
]
Hudson commented on AMBARI-20034:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6851 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6851/])
AMBARI-20034. USER to GROUP mapping (hdfs_user -> hadoop_group) should
(jluniya:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3809bdc6d5fe367c2c3207812ee42856214db8de])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java
> USER to GROUP mapping (hdfs_user -> hadoop_group) should be stack driven
> ------------------------------------------------------------------------
>
> Key: AMBARI-20034
> URL: https://issues.apache.org/jira/browse/AMBARI-20034
> Project: Ambari
> Issue Type: Bug
> Reporter: Madhuvanthi Radhakrishnan
> Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
> Attachments: AMBARI-20034_2.5_addendum.patch, AMBARI-20034_2.5.patch,
> AMBARI-20034.patch, AMBARI_20034_trunk_addendum.patch,
> AMBARI-20034_trunk.patch
>
>
> There is a hard coded logic to creating the user-group mapping for services.
> This presents an issue for custom services. Fix is to make it stack driven by
> connecting user to its groups within the configuration/stack definition itself
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
