[
https://issues.apache.org/jira/browse/AMBARI-21729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16128557#comment-16128557
]
Hadoop QA commented on AMBARI-21729:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12882099/AMBARI-21729_2.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12002//console
This message is automatically generated.
> Owner of yarn.include stays to be root:root where as dfs.include gets changed
> to the correct one upon restart services
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-21729
> URL: https://issues.apache.org/jira/browse/AMBARI-21729
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
> Affects Versions: 2.5.2
> Reporter: Dhanya Balasundaran
> Assignee: Dmytro Sen
> Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21729_2.patch, AMBARI-21729.patch
>
>
> - After deployment, create dfs.include and yarn.include in /etc/hadoop/conf
> as root user itself. - Set manage.include.files to true for HDFS and YARN and
> update dfs.hosts and yarn.resourcemanager.nodes.include-path properties
> - Restart services
> - After services are restrated dfs.include gets the right owner
> (<serviceuser>:hadoop) where as yarn.include still has root:root
> - Noticed that owner of dfs.include is updated during Namenode restart but
> yarn.include is not updated after restart of all services that had stale
> configs
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
