[OOZIE-1514] Rerunning a coordinator with no input dependencies puts actions in WAITING instead of READY and proceeding

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 4.0.0
• Fix Version/s: 4.0.0
• Assignee: Bowen Zhang
• Reporter: Mona Chitnis
• Created: 26/Aug/13 17:57
• Updated: 03/Aug/16 18:56
• Resolved: 27/Aug/13 19:50

Description

Following issue reported by Bowen:

rerun oozie coordinator action that has no data dependency will make the action stuck in "WAITING" forever.
The issue has to do with the change introduced in coordActionInputCheckXCommand. The rerun action will fail this if statement:
if (!nonExistListStr.equals(missingDeps))
since nonExistListStr and missingDeps are both empty strings. Once it fails the if statement, isChangeDependency is still
set to false and the status change to "READY" will not be persisted since we will call CoordActionUpdateForModifiedTimeJPAExecutor instead of CoordActionUpdateForInputCheckJPAExecutor in the updateCoordAction method.
the Action is in "WAITING" stage forever.