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

Hudson commented on AMBARI-17520:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #5228 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5228/])
AMBARI-17520.  Update the policy_user property to use storm user (rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bd99d76d3bc78e680e426970714b9ec18340a085])
* 
ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py
* 
ambari-server/src/main/resources/common-services/STORM/0.9.3/configuration/ranger-storm-plugin-properties.xml


> Update the policy_user property to use storm user principal specified in 
> Storms config
> --------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17520
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17520
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Gautam Borad
>            Assignee: Gautam Borad
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17520.patch
>
>
> Update the {{policy_user}} property in Advanced 
> ranger-storm-plugin-properties of Ranger with the value of the storm user 
> bare principal specified in Storms Ambari config.
> With this the principal used for storm will also be added to default ranger 
> policy and will prevent Storm service check failures.



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

Reply via email to