[ 
https://issues.apache.org/jira/browse/AMBARI-18235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431843#comment-15431843
 ] 

Hudson commented on AMBARI-18235:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5572 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5572/])
AMBARI-18235. Atlas file permissions of (afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=79588cedb46e794158b1b2516477c12d3701c785])
* (edit) ambari-server/src/test/python/stacks/2.5/configs/default.json
* (edit) ambari-server/src/test/python/stacks/2.3/configs/default.json
* (edit) ambari-server/src/test/python/stacks/2.3/configs/secure.json
* (edit) ambari-server/src/test/python/stacks/2.5/ATLAS/test_atlas_server.py
* (edit) 
ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py
* (edit) ambari-server/src/test/python/stacks/2.3/ATLAS/test_metadata_server.py


> Atlas file permissions of /var/lib/ambari-agent/tmp/atlas_hbase_setup.rb need 
> to be ${hbase_user}:${hadoop_group}
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-18235
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18235
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 2.4.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>            Priority: Critical
>             Fix For: trunk
>
>         Attachments: AMBARI-18235.patch
>
>
> Atlas generates the /var/lib/ambari-agent/tmp/atlas_hbase_setup.rb file that 
> is needed to grant permissions to the Atlas tables in HBASE.
> However, if Ambari agent is running as non-root, executing the file will fail 
> since the current ownership is root:root instead of 
> {noformat}${hbase_user}:${hadoop_group}{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to