[
https://issues.apache.org/jira/browse/AMBARI-9947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349080#comment-14349080
]
Hadoop QA commented on AMBARI-9947:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12702840/AMBARI-9947.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 1 new
or modified test files.
{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/1934//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1934//console
This message is automatically generated.
> Oozie alert after ambari upgrade 1.7.0->2.0.0 secured cluster
> -------------------------------------------------------------
>
> Key: AMBARI-9947
> URL: https://issues.apache.org/jira/browse/AMBARI-9947
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: AMBARI-9947.patch
>
>
> After upgrading secured cluster and restarting all services oozie has warning
> alert:
> Oozie Server Web UI
> HTTP 500 response in 0.000 seconds
> STR:
> 1. Installed ambari 1.7.0 on 3-node cluster, all services
> 2. Enabl security
> 3. Upgrade ambari to 2.0.0
> 4. Stop all services
> 5. Start all services
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)