[
https://issues.apache.org/jira/browse/AMBARI-13354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948548#comment-14948548
]
Hadoop QA commented on AMBARI-13354:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12765570/AMBARI-13354.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3925//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3925//console
This message is automatically generated.
> Ambari is not able to run Oozie Server which configured with different
> username than oozie
> ------------------------------------------------------------------------------------------
>
> Key: AMBARI-13354
> URL: https://issues.apache.org/jira/browse/AMBARI-13354
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.1.3
>
> Attachments: AMBARI-13354.patch
>
>
> Ambari is not able to run Oozie Server which configured with a different
> username than oozie.
> REPRODUCE: updating Ambari from 1.6 to 2.1 with a different username than
> oozie.
> Deleted the share in order for it to start
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
