[
https://issues.apache.org/jira/browse/OOZIE-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996168#comment-13996168
]
Hadoop QA commented on OOZIE-1831:
----------------------------------
Testing JIRA OOZIE-1831
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: 1439
. Tests failed: 2
. Tests errors: 2
. The patch failed the following testcases:
.
testCoordinatorActionCommandsSubmitAndStart(org.apache.oozie.sla.TestSLAEventGeneration)
.
testBundleEngineChange(org.apache.oozie.servlet.TestV1JobServletBundleEngine)
{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/1233/
> Oozie upgrade fails if workflow jobs are in running or suspended state
> ----------------------------------------------------------------------
>
> Key: OOZIE-1831
> URL: https://issues.apache.org/jira/browse/OOZIE-1831
> Project: Oozie
> Issue Type: Bug
> Components: tools
> Affects Versions: 4.1.0
> Reporter: Satish Mittal
> Assignee: Satish Mittal
> Fix For: 4.1.0
>
> Attachments: OOZIE-1831.patch.txt
>
>
> While upgrading oozie from 3.x to trunk, oozie upgrade fails if there any
> workflow jobs found in running or suspended state:
> {noformat}
> Error: There are [26] workflows in RUNNING/SUSPENDED state, they must
> complete or be killed
> Stack trace for the error was (for debug purposes):
> --------------------------------------
> java.lang.Exception: There are [26] workflows in RUNNING/SUSPENDED state,
> they must complete or be killed
> at org.apache.oozie.tools.OozieDBCLI.verifyDBState(OozieDBCLI.java:992)
> at org.apache.oozie.tools.OozieDBCLI.upgradeDB(OozieDBCLI.java:197)
> at org.apache.oozie.tools.OozieDBCLI.run(OozieDBCLI.java:128)
> at org.apache.oozie.tools.OozieDBCLI.main(OozieDBCLI.java:76)
> {noformat}
> This check seems unnecessary. It may not be possible to ensure in production
> that no workflows are in running/suspended state before upgrade.
> Also current upgrade code updates the status of coord jobs/coord actions in
> DB. This may not be required now.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
