[
https://issues.apache.org/jira/browse/OOZIE-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720778#comment-14720778
]
Hadoop QA commented on OOZIE-2318:
----------------------------------
Testing JIRA OOZIE-2318
Cleaning local git workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than
132
. {color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
. Tests run: 1690
. Tests failed: 5
. Tests errors: 0
. The patch failed the following testcases:
.
testBundleStatusTransitWithLock(org.apache.oozie.service.TestStatusTransitService)
.
testCoordMaterializeTriggerService3(org.apache.oozie.service.TestCoordMaterializeTriggerService)
.
testMaxMatThrottleNotPicked(org.apache.oozie.service.TestCoordMaterializeTriggerService)
.
testActionKillCommandDate(org.apache.oozie.command.coord.TestCoordActionsKillXCommand)
. testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/2523/
> Provide better solution for specifying SSL truststore to Oozie Client
> ---------------------------------------------------------------------
>
> Key: OOZIE-2318
> URL: https://issues.apache.org/jira/browse/OOZIE-2318
> Project: Oozie
> Issue Type: Sub-task
> Components: docs
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Fix For: trunk
>
> Attachments: OOZIE-2318.001.patch
>
>
> When using a self-signed certificate, Java will not allow the Oozie CLI will
> not connect to the Oozie server without importing the cert into the JRE, as
> described in the docs
> [here|http://oozie.apache.org/docs/4.2.0/AG_Install.html#Configure_the_Oozie_Client_to_connect_using_SSL_HTTPS].
> This has a number of downsides.
> Instead, we should get rid of that and replace it with directions on how to
> change where the Oozie CLI looks for the truststore:
> {noformat}
> export
> OOZIE_CLIENT_OPTS='-Djavax.net.ssl.trustStore=/path/to/oozie-truststore.jks
> -Djavax.net.ssl.trustStorePassword=password'
> {noformat}
> Along with directions on how to create the truststore from the keystore/cert.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
