You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2015/11/12 12:50:11 UTC

[jira] [Created] (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

Andrew Onischuk created AMBARI-13855:
----------------------------------------

             Summary: 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)