You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Nate Cole (JIRA)" <ji...@apache.org> on 2014/07/14 20:48:05 UTC
[jira] [Commented] (AMBARI-5367) Oozie directory on HDFS with
incorrect owner
[ https://issues.apache.org/jira/browse/AMBARI-5367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061015#comment-14061015 ]
Nate Cole commented on AMBARI-5367:
-----------------------------------
Hi [~Slaytanic], the product no longer contains the Puppet script you changed - can you make the same changes (if needed) to the Python-based scripts available on trunk? Thanks!
> Oozie directory on HDFS with incorrect owner
> --------------------------------------------
>
> Key: AMBARI-5367
> URL: https://issues.apache.org/jira/browse/AMBARI-5367
> Project: Ambari
> Issue Type: Bug
> Components: agent
> Affects Versions: 1.5.0, 1.5.1, 1.4.4
> Environment: Centos 6 SuSE 11 CentOS 5
> Reporter: Lei Xiang
> Assignee: Lei Xiang
> Priority: Critical
> Labels: ambari-agent
> Fix For: 1.7.0
>
> Attachments: AMBARI-5367.patch
>
>
> From ambari 1.4.4-1.5.1, there is a puppet missing for Oozie server start, may cause oozie server startup error. Oozie server will not start.
> The problem is , when oozie installed, the owner of oozie's directory on HDFS (/user/oozie) is not oozie:hdfs, so puppet cannot copy any thing to /user/oozie and the the oozie server start process hangs up.
--
This message was sent by Atlassian JIRA
(v6.2#6252)