[
https://issues.apache.org/jira/browse/AMBARI-9377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302222#comment-14302222
]
Hudson commented on AMBARI-9377:
--------------------------------
FAILURE: Integrated in Ambari-trunk-Commit-docker #841 (See
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/841/])
AMBARI-9377. hdfs superuser (usually user 'hdfs') should be in group
dfs.cluster.administrators (aonishuk) (aonishuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d2af57f63dbd6839eaae1d408e4c2425e8bb58f0)
* ambari-server/src/test/python/stacks/2.0.6/hooks/before-ANY/test_before_any.py
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hdfs-site.xml
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/params.py
> hdfs superuser (usually user 'hdfs') should be in group
> dfs.cluster.administrators
> ----------------------------------------------------------------------------------
>
> Key: AMBARI-9377
> URL: https://issues.apache.org/jira/browse/AMBARI-9377
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.0.0
>
>
> Noticed this on a HA cluster where the dfsadmin fetch image call failed with a
> 403 error.
> Fetch image call uses the value in dfs.cluster.administrators (hdfs-site.xml)
> to determine who the admin is. That is set to group hdfs. Other dfsadmin calls
> as user hdfs who belongs to group hadoop go through. But fetch image does not
> as hdfs does not belong to group hadoop. We should either add hdfs user to
> group hdfs or change this property to be set to group hadoop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
