[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (107 issues) Subscriber: ooziedaily Key Summary OOZIE-3186 Oozie is unable to use configuration linked using jceks://file/... https://issues.apache.org/jira/browse/OOZIE-3186 OOZIE-3182 Oozie components fail with checkstyle errors https://issues.apache.org/jira/browse/OOZIE-3182 OOZIE-3179 Adding a configurable config-default.xml location to a workflow https://issues.apache.org/jira/browse/OOZIE-3179 OOZIE-3176 Oozie-core fails with checkstyle errors. https://issues.apache.org/jira/browse/OOZIE-3176 OOZIE-3170 Oozie Diagnostic Bundle tool fails with NPE due to missing service class https://issues.apache.org/jira/browse/OOZIE-3170 OOZIE-3135 Configure log4j2 in SqoopMain https://issues.apache.org/jira/browse/OOZIE-3135 OOZIE-3134 Potential inconsistency between the in-memory SLA map and the Oozie database https://issues.apache.org/jira/browse/OOZIE-3134 OOZIE-3109 Escape log-streaming's HTML-specific characters https://issues.apache.org/jira/browse/OOZIE-3109 OOZIE-3105 testJMXInstrumentation from the org.apache.oozie.util.TestMetricsInstrumentation class is flaky https://issues.apache.org/jira/browse/OOZIE-3105 OOZIE-3094 fix for grammar mistake https://issues.apache.org/jira/browse/OOZIE-3094 OOZIE-3091 Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: org/apache/avro/mapred/AvroWrapper" https://issues.apache.org/jira/browse/OOZIE-3091 OOZIE-3071 Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than Spark 2.2.0 https://issues.apache.org/jira/browse/OOZIE-3071 OOZIE-3063 Sanitizing variables that are part of openjpa.ConnectionProperties https://issues.apache.org/jira/browse/OOZIE-3063 OOZIE-3062 Set HADOOP_CONF_DIR for spark action https://issues.apache.org/jira/browse/OOZIE-3062 OOZIE-3061 Kill only those child jobs which are not already killed https://issues.apache.org/jira/browse/OOZIE-3061 OOZIE-3002 address findbugs errors in client lib https://issues.apache.org/jira/browse/OOZIE-3002 OOZIE-2975 code clean up in pig sharelib, replace Exception with more explicit, add try with resources, StringBuilder instead of StringBuffer https://issues.apache.org/jira/browse/OOZIE-2975 OOZIE-2957 Documentation states that starting a coordinator is possible https://issues.apache.org/jira/browse/OOZIE-2957 OOZIE-2956 Fix Findbugs warnings related to reliance on default encoding in oozie-core https://issues.apache.org/jira/browse/OOZIE-2956 OOZIE-2955 Fix Findbugs warnings related to reliance on default encoding in oozie-client https://issues.apache.org/jira/browse/OOZIE-2955 OOZIE-2954 Fix Checkstyle issues in oozie-client https://issues.apache.org/jira/browse/OOZIE-2954 OOZIE-2953 Fix Checkstyle issues in oozie-tools https://issues.apache.org/jira/browse/OOZIE-2953 OOZIE-2952 Fix Findbugs warnings in oozie-sharelib-oozie https://issues.apache.org/jira/browse/OOZIE-2952 OOZIE-2949 Escape quotes whitespaces in Sqoop field https://issues.apache.org/jira/browse/OOZIE-2949 OOZIE-2942 Fix Findbugs warnings in oozie-examples https://issues.apache.org/jira/browse/OOZIE-2942 OOZIE-2937 Remove redundant groupId from the child pom's https://issues.apache.org/jira/browse/OOZIE-2937 OOZIE-2934 Fix "Exceptional return value of java.io.File.mkdirs() ignored" Findbugs error in oozie-sharelib-spark https://issues.apache.org/jira/browse/OOZIE-2934 OOZIE-2927 Append new line character for Hive2 query using query tag https://issues.apache.org/jira/browse/OOZIE-2927 OOZIE-2914 Consolidate Trim https://issues.apache.org/jira/browse/OOZIE-2914 OOZIE-2883 OOZIE throw the error "Missing [oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups] property" https://issues.apache.org/jira/browse/OOZIE-2883 OOZIE-2877 Oozie Git Action https://issues.apache.org/jira/browse/OOZIE-2877 OOZIE-2867 Timezone handling for Coordinators: emphasize "Continent/City" format https://issues.apache.org/jira/browse/OOZIE-2867 OOZIE-2834 ParameterVerifier logging non-useful warning for workflow definition https://issues.apache.org/jira/browse/OOZIE-2834 OOZIE-2833 when using uber mode the regex pattern used in the extractHeapSizeMB method does not allow heap sizes specified in bytes. https://issues.apache.org/jira/browse/OOZIE-2833 OOZIE-2829 Improve sharelib upload to accept multiple source folders https://issues.apache.org/jira/browse/OOZIE-2829 OOZIE-2826 Falcon feed fails to aws s3; Oozie joda time version does not meet required jar version 2.2 or later
Failed: OOZIE-3186 PreCommit Build #411
Jira: https://issues.apache.org/jira/browse/OOZIE-3186
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/411/
###
## LAST 100 LINES OF THE CONSOLE
###
[...truncated 1.71 MB...]
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2253 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
removed
[TRACE] File
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
removed
Running test-patch task BACKWARDS_COMPATIBILITY
Running test-patch task TESTS
Running test-patch task DISTRO
Testing JIRA OOZIE-3186
Cleaning local git workspace
+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
+1 There are no new bugs found in [webapp].
+1 There are no new bugs found in [core].
+1 There are no new bugs found in [tools].
+1 There are no new bugs found in [sharelib/hive2].
+1 There are no new bugs found in [sharelib/distcp].
+1 There are no new bugs found in [sharelib/hcatalog].
+1 There are no new bugs found in [sharelib/streaming].
+1 There are no new bugs found in [sharelib/sqoop].
+1 There are no new bugs found in [sharelib/oozie].
+1 There are no new bugs found in [sharelib/pig].
+1 There are no new bugs found in [sharelib/hive].
+1 There are no new bugs found in [sharelib/spark].
+1 There are no new bugs found in [client].
+1 There are no new bugs found in [examples].
+1 There are no new bugs found in [docs].
+1 There are no new bugs found in [server].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run: 2092
Tests failed: 3
Tests errors: 2
The patch failed the following testcases:
testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerService)
testConnectionContext(org.apache.oozie.service.TestJMSAccessorService)
testHiveAction(org.apache.oozie.action.hadoop.TestHiveActionExecutor)
Tests failing with errors:
testConnectionRetryExceptionListener(org.apache.oozie.service.TestJMSAccessorService)
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)
Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
TestCoordMaterializeTriggerService#testCoordMaterializeTriggerService3
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch
-1 Overall result, please check the reported -1(s)
There is at least one warning, please check
The full output of the test-patch run is available at
https://builds.apache.org/job/PreCommit-OOZIE-Build/411/
Adding comment to JIRA
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:--
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/13141469/comment/16380290","id":"16380290","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
at hadoop dot apache dot
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small=hadoopqa=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall=hadoopqa=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium=hadoopqa=10393"},"displayName":"Hadoop
QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting JIRA
OOZIE-3186\n\nCleaning local git
workspace\n\n\n\n{color:green}+1
PATCH_APPLIES{color}\n{color:green}+1 CLEAN{color}\n{color:red}-1
RAW_PATCH_ANALYSIS{color}\n.{color:green}+1{color} the patch does not
introduce any
[jira] [Updated] (OOZIE-3187) coordinator: EL function to get coordinator information: last successful run, last run status, ...
[ https://issues.apache.org/jira/browse/OOZIE-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruben Van Wanzeele updated OOZIE-3187: -- Issue Type: New Feature (was: Bug) > coordinator: EL function to get coordinator information: last successful run, > last run status, ... > -- > > Key: OOZIE-3187 > URL: https://issues.apache.org/jira/browse/OOZIE-3187 > Project: Oozie > Issue Type: New Feature > Components: coordinator >Affects Versions: 4.2.0 >Reporter: Ruben Van Wanzeele >Priority: Major > > It would be handy if I could retrieve the last successful run of my > coordinator job and pass that as a property to my workflow. > I tried to manage this, but there is no such function. Currently, you cannot > retrieve any information about the coordinator job. I could think of other > useful info such as: > * status last run > * errorcode last run > * amount of running instances > * ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OOZIE-3187) coordinator: EL function to get coordinator information: last successful run, last run status, ...
Ruben Van Wanzeele created OOZIE-3187: - Summary: coordinator: EL function to get coordinator information: last successful run, last run status, ... Key: OOZIE-3187 URL: https://issues.apache.org/jira/browse/OOZIE-3187 Project: Oozie Issue Type: Bug Components: coordinator Affects Versions: 4.2.0 Reporter: Ruben Van Wanzeele It would be handy if I could retrieve the last successful run of my coordinator job and pass that as a property to my workflow. I tried to manage this, but there is no such function. Currently, you cannot retrieve any information about the coordinator job. I could think of other useful info such as: * status last run * errorcode last run * amount of running instances * ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3186) Oozie is unable to use configuration linked using jceks://file/...
[
https://issues.apache.org/jira/browse/OOZIE-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380290#comment-16380290
]
Hadoop QA commented on OOZIE-3186:
--
Testing JIRA OOZIE-3186
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:red}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{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{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [server].
{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: 2092
.Tests failed: 3
.Tests errors: 2
.The patch failed the following testcases:
testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerService)
testConnectionContext(org.apache.oozie.service.TestJMSAccessorService)
testHiveAction(org.apache.oozie.action.hadoop.TestHiveActionExecutor)
.Tests failing with errors:
testConnectionRetryExceptionListener(org.apache.oozie.service.TestJMSAccessorService)
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)
.{color:orange}Tests failed at first run:{color}
TestJavaActionExecutor#testCredentialsSkip
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
TestCoordMaterializeTriggerService#testCoordMaterializeTriggerService3
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{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}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/411/
> Oozie is unable to use configuration linked using jceks://file/...
> --
>
> Key: OOZIE-3186
> URL: https://issues.apache.org/jira/browse/OOZIE-3186
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 5.0.0b1, 5.0.0, 4.3.1
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Major
> Labels: usability
> Attachments: OOZIE-3186-001.patch, OOZIE-3186-002.patch
>
>
> When Oozie is used with Ambari, the next configuration makes Oozie fail to
> start:
> {noformat}
>
> hadoop.security.credential.provider.path
> jceks://file/.../oozie-site.jceks
>
> {noformat}
> Value should have *localjceks://* instead of *jceks://*. But Ambari does not
> let change this value. I propose change the url when Oozie loads it.
>
> Stacktrace, when the issue occurs:
> {noformat}
> org.apache.oozie.service.ServiceException: E0103: Could not load
[jira] [Commented] (OOZIE-3186) Oozie is unable to use configuration linked using jceks://file/...
[
https://issues.apache.org/jira/browse/OOZIE-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380025#comment-16380025
]
Hadoop QA commented on OOZIE-3186:
--
PreCommit-OOZIE-Build started
> Oozie is unable to use configuration linked using jceks://file/...
> --
>
> Key: OOZIE-3186
> URL: https://issues.apache.org/jira/browse/OOZIE-3186
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 5.0.0b1, 5.0.0, 4.3.1
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Major
> Labels: usability
> Attachments: OOZIE-3186-001.patch
>
>
> When Oozie is used with Ambari, the next configuration makes Oozie fail to
> start:
> {noformat}
>
> hadoop.security.credential.provider.path
> jceks://file/.../oozie-site.jceks
>
> {noformat}
> Value should have *localjceks://* instead of *jceks://*. But Ambari does not
> let change this value. I propose change the url when Oozie loads it.
>
> Stacktrace, when the issue occurs:
> {noformat}
> org.apache.oozie.service.ServiceException: E0103: Could not load service
> classes, Could not load password for [oozie.service.JPAService.jdbc.password]
> at org.apache.oozie.service.Services.loadServices(Services.java:309) at
> org.apache.oozie.service.Services.init(Services.java:213) at
> org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:46)
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4276)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4779)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:803)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:780)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:583) at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:944) at
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:779) at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:505) at
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1322) at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:325) at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1069) at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:822) at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061) at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) at
> org.apache.catalina.core.StandardService.start(StandardService.java:525) at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:761) at
> org.apache.catalina.startup.Catalina.start(Catalina.java:595) at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at
> org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Caused by:
> java.lang.IllegalArgumentException: Could not load password for
> [oozie.service.JPAService.jdbc.password] at
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:615)
> at
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:602)
> at org.apache.oozie.service.JPAService.init(JPAService.java:147) at
> org.apache.oozie.service.Services.setServiceInternal(Services.java:386) at
> org.apache.oozie.service.Services.setService(Services.java:372) at
> org.apache.oozie.service.Services.loadServices(Services.java:305) ... 26 more
> Caused by: java.lang.reflect.InvocationTargetException at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:608)
> ... 31 more Caused by: java.lang.UnsupportedOperationException: Accessing
> local file system is not allowed at
> org.apache.hadoop.fs.RawLocalFileSystem.initialize(RawLocalFileSystem.java:48)
> at org.apache.hadoop.fs.LocalFileSystem.initialize(LocalFileSystem.java:47)
> at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795) at
> org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99) at
>
[jira] [Created] (OOZIE-3186) Oozie is unable to use configuration linked using jceks://file/...
Denes Bodo created OOZIE-3186:
-
Summary: Oozie is unable to use configuration linked using
jceks://file/...
Key: OOZIE-3186
URL: https://issues.apache.org/jira/browse/OOZIE-3186
Project: Oozie
Issue Type: Bug
Components: core
Affects Versions: 4.3.1, 5.0.0b1, 5.0.0
Reporter: Denes Bodo
Assignee: Denes Bodo
When Oozie is used with Ambari, the next configuration makes Oozie fail to
start:
{noformat}
hadoop.security.credential.provider.path
jceks://file/.../oozie-site.jceks
{noformat}
Value should have *localjceks://* instead of *jceks://*. But Ambari does not
let change this value. I propose change the url when Oozie loads it.
Stacktrace, when the issue occurs:
{noformat}
org.apache.oozie.service.ServiceException: E0103: Could not load service
classes, Could not load password for [oozie.service.JPAService.jdbc.password]
at org.apache.oozie.service.Services.loadServices(Services.java:309) at
org.apache.oozie.service.Services.init(Services.java:213) at
org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:46)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4276)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4779)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:803)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:780) at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:583) at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:944) at
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:779) at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:505) at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1322) at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:325) at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1069) at
org.apache.catalina.core.StandardHost.start(StandardHost.java:822) at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061) at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) at
org.apache.catalina.core.StandardService.start(StandardService.java:525) at
org.apache.catalina.core.StandardServer.start(StandardServer.java:761) at
org.apache.catalina.startup.Catalina.start(Catalina.java:595) at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498) at
org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Caused by:
java.lang.IllegalArgumentException: Could not load password for
[oozie.service.JPAService.jdbc.password] at
org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:615)
at
org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:602)
at org.apache.oozie.service.JPAService.init(JPAService.java:147) at
org.apache.oozie.service.Services.setServiceInternal(Services.java:386) at
org.apache.oozie.service.Services.setService(Services.java:372) at
org.apache.oozie.service.Services.loadServices(Services.java:305) ... 26 more
Caused by: java.lang.reflect.InvocationTargetException at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498) at
org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:608)
... 31 more Caused by: java.lang.UnsupportedOperationException: Accessing
local file system is not allowed at
org.apache.hadoop.fs.RawLocalFileSystem.initialize(RawLocalFileSystem.java:48)
at org.apache.hadoop.fs.LocalFileSystem.initialize(LocalFileSystem.java:47) at
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795) at
org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99) at
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2829) at
org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2811) at
org.apache.hadoop.fs.FileSystem.get(FileSystem.java:390) at
org.apache.hadoop.fs.Path.getFileSystem(Path.java:295) at
org.apache.hadoop.security.alias.JavaKeyStoreProvider.initFileSystem(JavaKeyStoreProvider.java:89)
at
org.apache.hadoop.security.alias.AbstractJavaKeyStoreProvider.(AbstractJavaKeyStoreProvider.java:82)
at
[jira] [Updated] (OOZIE-3186) Oozie is unable to use configuration linked using jceks://file/...
[
https://issues.apache.org/jira/browse/OOZIE-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denes Bodo updated OOZIE-3186:
--
Attachment: OOZIE-3186-001.patch
> Oozie is unable to use configuration linked using jceks://file/...
> --
>
> Key: OOZIE-3186
> URL: https://issues.apache.org/jira/browse/OOZIE-3186
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 5.0.0b1, 5.0.0, 4.3.1
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Major
> Labels: usability
> Attachments: OOZIE-3186-001.patch
>
>
> When Oozie is used with Ambari, the next configuration makes Oozie fail to
> start:
> {noformat}
>
> hadoop.security.credential.provider.path
> jceks://file/.../oozie-site.jceks
>
> {noformat}
> Value should have *localjceks://* instead of *jceks://*. But Ambari does not
> let change this value. I propose change the url when Oozie loads it.
>
> Stacktrace, when the issue occurs:
> {noformat}
> org.apache.oozie.service.ServiceException: E0103: Could not load service
> classes, Could not load password for [oozie.service.JPAService.jdbc.password]
> at org.apache.oozie.service.Services.loadServices(Services.java:309) at
> org.apache.oozie.service.Services.init(Services.java:213) at
> org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:46)
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4276)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4779)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:803)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:780)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:583) at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:944) at
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:779) at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:505) at
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1322) at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:325) at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1069) at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:822) at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061) at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) at
> org.apache.catalina.core.StandardService.start(StandardService.java:525) at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:761) at
> org.apache.catalina.startup.Catalina.start(Catalina.java:595) at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at
> org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Caused by:
> java.lang.IllegalArgumentException: Could not load password for
> [oozie.service.JPAService.jdbc.password] at
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:615)
> at
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:602)
> at org.apache.oozie.service.JPAService.init(JPAService.java:147) at
> org.apache.oozie.service.Services.setServiceInternal(Services.java:386) at
> org.apache.oozie.service.Services.setService(Services.java:372) at
> org.apache.oozie.service.Services.loadServices(Services.java:305) ... 26 more
> Caused by: java.lang.reflect.InvocationTargetException at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:608)
> ... 31 more Caused by: java.lang.UnsupportedOperationException: Accessing
> local file system is not allowed at
> org.apache.hadoop.fs.RawLocalFileSystem.initialize(RawLocalFileSystem.java:48)
> at org.apache.hadoop.fs.LocalFileSystem.initialize(LocalFileSystem.java:47)
> at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795) at
> org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99) at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2829)
[jira] [Commented] (OOZIE-3186) Oozie is unable to use configuration linked using jceks://file/...
[
https://issues.apache.org/jira/browse/OOZIE-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380147#comment-16380147
]
Hadoop QA commented on OOZIE-3186:
--
PreCommit-OOZIE-Build started
> Oozie is unable to use configuration linked using jceks://file/...
> --
>
> Key: OOZIE-3186
> URL: https://issues.apache.org/jira/browse/OOZIE-3186
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 5.0.0b1, 5.0.0, 4.3.1
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Major
> Labels: usability
> Attachments: OOZIE-3186-001.patch, OOZIE-3186-002.patch
>
>
> When Oozie is used with Ambari, the next configuration makes Oozie fail to
> start:
> {noformat}
>
> hadoop.security.credential.provider.path
> jceks://file/.../oozie-site.jceks
>
> {noformat}
> Value should have *localjceks://* instead of *jceks://*. But Ambari does not
> let change this value. I propose change the url when Oozie loads it.
>
> Stacktrace, when the issue occurs:
> {noformat}
> org.apache.oozie.service.ServiceException: E0103: Could not load service
> classes, Could not load password for [oozie.service.JPAService.jdbc.password]
> at org.apache.oozie.service.Services.loadServices(Services.java:309) at
> org.apache.oozie.service.Services.init(Services.java:213) at
> org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:46)
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4276)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4779)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:803)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:780)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:583) at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:944) at
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:779) at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:505) at
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1322) at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:325) at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1069) at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:822) at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061) at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) at
> org.apache.catalina.core.StandardService.start(StandardService.java:525) at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:761) at
> org.apache.catalina.startup.Catalina.start(Catalina.java:595) at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at
> org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Caused by:
> java.lang.IllegalArgumentException: Could not load password for
> [oozie.service.JPAService.jdbc.password] at
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:615)
> at
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:602)
> at org.apache.oozie.service.JPAService.init(JPAService.java:147) at
> org.apache.oozie.service.Services.setServiceInternal(Services.java:386) at
> org.apache.oozie.service.Services.setService(Services.java:372) at
> org.apache.oozie.service.Services.loadServices(Services.java:305) ... 26 more
> Caused by: java.lang.reflect.InvocationTargetException at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:608)
> ... 31 more Caused by: java.lang.UnsupportedOperationException: Accessing
> local file system is not allowed at
> org.apache.hadoop.fs.RawLocalFileSystem.initialize(RawLocalFileSystem.java:48)
> at org.apache.hadoop.fs.LocalFileSystem.initialize(LocalFileSystem.java:47)
> at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795) at
> org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99) at
>
[jira] [Commented] (OOZIE-3186) Oozie is unable to use configuration linked using jceks://file/...
[
https://issues.apache.org/jira/browse/OOZIE-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380146#comment-16380146
]
Hadoop QA commented on OOZIE-3186:
--
Testing JIRA OOZIE-3186
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:red}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{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{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [tools].
{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:green}+1 TESTS{color}
.Tests run: 2092
.{color:orange}Tests failed at first run:{color}
TestJMSJobEventListener#testConnectionDrop
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{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}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/410/
> Oozie is unable to use configuration linked using jceks://file/...
> --
>
> Key: OOZIE-3186
> URL: https://issues.apache.org/jira/browse/OOZIE-3186
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 5.0.0b1, 5.0.0, 4.3.1
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Major
> Labels: usability
> Attachments: OOZIE-3186-001.patch, OOZIE-3186-002.patch
>
>
> When Oozie is used with Ambari, the next configuration makes Oozie fail to
> start:
> {noformat}
>
> hadoop.security.credential.provider.path
> jceks://file/.../oozie-site.jceks
>
> {noformat}
> Value should have *localjceks://* instead of *jceks://*. But Ambari does not
> let change this value. I propose change the url when Oozie loads it.
>
> Stacktrace, when the issue occurs:
> {noformat}
> org.apache.oozie.service.ServiceException: E0103: Could not load service
> classes, Could not load password for [oozie.service.JPAService.jdbc.password]
> at org.apache.oozie.service.Services.loadServices(Services.java:309) at
> org.apache.oozie.service.Services.init(Services.java:213) at
> org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:46)
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4276)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4779)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:803)
> at
[jira] [Updated] (OOZIE-3186) Oozie is unable to use configuration linked using jceks://file/...
[
https://issues.apache.org/jira/browse/OOZIE-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denes Bodo updated OOZIE-3186:
--
Attachment: OOZIE-3186-002.patch
> Oozie is unable to use configuration linked using jceks://file/...
> --
>
> Key: OOZIE-3186
> URL: https://issues.apache.org/jira/browse/OOZIE-3186
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 5.0.0b1, 5.0.0, 4.3.1
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Major
> Labels: usability
> Attachments: OOZIE-3186-001.patch, OOZIE-3186-002.patch
>
>
> When Oozie is used with Ambari, the next configuration makes Oozie fail to
> start:
> {noformat}
>
> hadoop.security.credential.provider.path
> jceks://file/.../oozie-site.jceks
>
> {noformat}
> Value should have *localjceks://* instead of *jceks://*. But Ambari does not
> let change this value. I propose change the url when Oozie loads it.
>
> Stacktrace, when the issue occurs:
> {noformat}
> org.apache.oozie.service.ServiceException: E0103: Could not load service
> classes, Could not load password for [oozie.service.JPAService.jdbc.password]
> at org.apache.oozie.service.Services.loadServices(Services.java:309) at
> org.apache.oozie.service.Services.init(Services.java:213) at
> org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:46)
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4276)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4779)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:803)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:780)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:583) at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:944) at
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:779) at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:505) at
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1322) at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:325) at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1069) at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:822) at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061) at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) at
> org.apache.catalina.core.StandardService.start(StandardService.java:525) at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:761) at
> org.apache.catalina.startup.Catalina.start(Catalina.java:595) at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at
> org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Caused by:
> java.lang.IllegalArgumentException: Could not load password for
> [oozie.service.JPAService.jdbc.password] at
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:615)
> at
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:602)
> at org.apache.oozie.service.JPAService.init(JPAService.java:147) at
> org.apache.oozie.service.Services.setServiceInternal(Services.java:386) at
> org.apache.oozie.service.Services.setService(Services.java:372) at
> org.apache.oozie.service.Services.loadServices(Services.java:305) ... 26 more
> Caused by: java.lang.reflect.InvocationTargetException at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:608)
> ... 31 more Caused by: java.lang.UnsupportedOperationException: Accessing
> local file system is not allowed at
> org.apache.hadoop.fs.RawLocalFileSystem.initialize(RawLocalFileSystem.java:48)
> at org.apache.hadoop.fs.LocalFileSystem.initialize(LocalFileSystem.java:47)
> at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795) at
> org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99) at
>
Failed: OOZIE-3186 PreCommit Build #410
Jira: https://issues.apache.org/jira/browse/OOZIE-3186
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/410/
###
## LAST 100 LINES OF THE CONSOLE
###
[...truncated 1.71 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/distcp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [docs].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [core].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [webapp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [tools].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2253 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
removed
[TRACE] File
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
removed
Running test-patch task BACKWARDS_COMPATIBILITY
Running test-patch task TESTS
Running test-patch task DISTRO
Testing JIRA OOZIE-3186
Cleaning local git workspace
+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
+1 There are no new bugs found in [client].
+1 There are no new bugs found in [sharelib/hive].
+1 There are no new bugs found in [sharelib/sqoop].
+1 There are no new bugs found in [sharelib/spark].
+1 There are no new bugs found in [sharelib/streaming].
+1 There are no new bugs found in [sharelib/hive2].
+1 There are no new bugs found in [sharelib/oozie].
+1 There are no new bugs found in [sharelib/hcatalog].
+1 There are no new bugs found in [sharelib/pig].
+1 There are no new bugs found in [sharelib/distcp].
+1 There are no new bugs found in [docs].
+1 There are no new bugs found in [server].
+1 There are no new bugs found in [core].
+1 There are no new bugs found in [examples].
+1 There are no new bugs found in [webapp].
+1 There are no new bugs found in [tools].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 2092
Tests failed at first run:
TestJMSJobEventListener#testConnectionDrop
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch
-1 Overall result, please check the reported -1(s)
There is at least one warning, please check
The full output of the test-patch run is available at
https://builds.apache.org/job/PreCommit-OOZIE-Build/410/
Adding comment to JIRA
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:--
0100 31400 0 100 3140 0 4759 --:--:-- --:--:-- --:--:--
4757{"self":"https://issues.apache.org/jira/rest/api/2/issue/13141469/comment/16380146","id":"16380146","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
at hadoop dot apache dot
