Description
We found that after OOZIE-1978 the attached workflow becomes invalid. Aa we found out the following line brings the problem: https://github.com/apache/oozie/commit/8e9b9042b3270dc5ff975c44a5c977fcc41250e4#diff-a38ae78886b7c3afb711d32cfb4dbbbdR267 . The parameter "okPath" changed from okPath to true.
The following workflow is problematic:
<workflow-app xmlns="uri:oozie:workflow:0.4" name="shell-fork-wf"> <start to="fork"/> <fork name="fork"> <path start="FA"/> <path start="FB"/> </fork> <action name="FA"> <shell xmlns="uri:oozie:shell-action:0.2"> <job-tracker>${jobTracker}</job-tracker> <name-node>${nameNode}</name-node> <exec>${myscript}</exec> <file>${myscriptPath}</file> <capture-output/> </shell> <ok to="join"/> <error to="D"/> </action> <action name="FB"> <shell xmlns="uri:oozie:shell-action:0.2"> <job-tracker>${jobTracker}</job-tracker> <name-node>${nameNode}</name-node> <exec>${myscript}</exec> <file>${myscriptPath}</file> <capture-output/> </shell> <ok to="join"/> <error to="D"/> </action> <join name="join" to="C" /> <action name="C"> <shell xmlns="uri:oozie:shell-action:0.2"> <job-tracker>${jobTracker}</job-tracker> <name-node>${nameNode}</name-node> <exec>${myscript}</exec> <file>${myscriptPath}</file> <capture-output/> </shell> <ok to="end"/> <error to="D"/> </action> <action name="D"> <shell xmlns="uri:oozie:shell-action:0.2"> <job-tracker>${jobTracker}</job-tracker> <name-node>${nameNode}</name-node> <exec>${myscript}</exec> <file>${myscriptPath}</file> <capture-output/> </shell> <ok to="E"/> <error to="fail"/> </action> <action name="E"> <shell xmlns="uri:oozie:shell-action:0.2"> <job-tracker>${jobTracker}</job-tracker> <name-node>${nameNode}</name-node> <exec>${myscript}</exec> <file>${myscriptPath}</file> <capture-output/> </shell> <ok to="fail"/> <error to="fail"/> </action> <kill name="fail"> <message>Shell action failed, error message[${wf:errorMessage(wf:lastErrorNode())}]</message> </kill> <end name="end"/> </workflow-app>