[
https://issues.apache.org/jira/browse/AMBARI-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539121#comment-14539121
]
Hadoop QA commented on AMBARI-11058:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12732081/AMBARI-11058.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 patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/2684//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2684//console
This message is automatically generated.
> Check oozie.https properties to generate oozie war -secure
> ----------------------------------------------------------
>
> Key: AMBARI-11058
> URL: https://issues.apache.org/jira/browse/AMBARI-11058
> Project: Ambari
> Issue Type: Bug
> Reporter: Tom Beerbower
> Assignee: Tom Beerbower
> Fix For: 1.2.1
>
> Attachments: AMBARI-11058.patch
>
>
> We should trigger a -secure prepare-war step if we notice any oozie.https.*
> properties added in the Custom oozie-site.
> {code}
> oozie.https.port=11443
> oozie.https.keystore.file=/home/oozie/.keystore
> oozie.https.keystore.pass=password
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
