ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-13855) Ambari does not change permissions and owner/group for log and PID directories during install on cluster with UMASK 027 + non-root agent
Date Thu, 12 Nov 2015 17:02:10 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-13855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Onischuk resolved AMBARI-13855.
--------------------------------------
    Resolution: Fixed

Committed to trunk

> Ambari does not change permissions and owner/group for log and PID directories during
install on cluster with UMASK 027 + non-root agent
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13855
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13855
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.1.3
>
>
> Steps:
>   1. Before deploy were created log and PID dirs with root owners, root group and 000
permissions.
>   2. Deployed cluster via blueprint.
> Result: some services (HDFS, MapReduce2, YARN, Hive) were started and log, pid
> dirs have valid credentials/owners/group, but a lot of services were failed
> (ZooKeeper, Knox, Ambari Metrics etc.), permissions/owners/groups were not
> changed.



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

Mime
View raw message