[
https://issues.apache.org/jira/browse/AMBARI-21588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16105085#comment-16105085
]
Hadoop QA commented on AMBARI-21588:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12879353/AMBARI-21588.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/11886//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11886//console
This message is automatically generated.
> MetadataServer start fails if Atlas service is started with custom service
> user.
> --------------------------------------------------------------------------------
>
> Key: AMBARI-21588
> URL: https://issues.apache.org/jira/browse/AMBARI-21588
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.2
> Reporter: Vishal Suvagia
> Assignee: Vishal Suvagia
> Fix For: 2.5.2
>
> Attachments: AMBARI-21588.patch
>
>
> File permissons for stack_root/current/atlas-server/server/webapp/atlas is
> root:root, when atlas user is custom, Atlas Metadata Server can not start.
> After changing permissions to the custom atlas user then Atlas was
> successfully started.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
