-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workflow stuck in running if it contains non-leaf-task onExit-handler #3431
Comments
Interestingly enough, this only happens with the
Working on finding a fix right now |
This has something to do with the unique nested dag structure |
This one is certainly a Heisenbug haha :) |
Found the issue: if |
Checklist:
What happened:
I created a dag where each task has an exit handler. In the example below, step-3 depends on step-2. After the fix of #3395 all exitHandlers are now being called as expected (thanks a lot to the team for this VERY quick fix). However the exitHandler of the non-leaf task never registers as finished and thus keeps the workflow in status running indefinitely.
What you expected to happen:
I expected the exitHandler to register as finished after its execution and the workflow to finish.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
It also seems like there is an issue with the execution of the exitHandler for non-leaf tasks if the exitHandler contains more than one task: #3432
These might be related?
Environment:
Other debugging information (if applicable):
Logs
see above
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: