You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/03/04 21:28:39 UTC
[jira] [Commented] (AMBARI-9932) Ambari chown Storm conf dir which
prevent start of storm worker in secure mode with runas enabled
[ https://issues.apache.org/jira/browse/AMBARI-9932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347514#comment-14347514 ]
Hudson commented on AMBARI-9932:
--------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #1948 (See [https://builds.apache.org/job/Ambari-trunk-Commit/1948/])
AMBARI-9932. Ambari chown Storm conf dir which prevent start of storm worker in secure mode with runas enabled. (mpapyrkovskyy) (mpapyrkovskyy: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6549fe8746392981cbf8a2009670750bc1085157)
* ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/storm.py
* ambari-server/src/test/python/stacks/2.1/STORM/test_storm_base.py
> Ambari chown Storm conf dir which prevent start of storm worker in secure mode with runas enabled
> -------------------------------------------------------------------------------------------------
>
> Key: AMBARI-9932
> URL: https://issues.apache.org/jira/browse/AMBARI-9932
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 1.7.0
> Reporter: Myroslav Papirkovskyy
> Assignee: Myroslav Papirkovskyy
> Priority: Critical
> Fix For: 2.0.0
>
>
> Secure Storm cannot be started in secure mode because Ambari overrides conf dir permissions.
> Follow steps:
> 1. change permissions
> {code}
> chown -R root:hadoop /etc/storm/conf/
> {code}
> 2. restart Storm via Ambari and check permission. Permission are reverted:
> {code}
> [root@falconf1 data]# ls -ld /etc/storm/conf
> drwxr-xr-x 2 storm hadoop 4096 Jan 11 00:42 /etc/storm/conf
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)