-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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 becomes completed before some template triggered by LifecycleHook Running
is completed
#11113
Closed
3 tasks done
Comments
@toyamagu-2021 this is an edge case. lifecycle hook node should update the status even workflow is completed. Do you like to submit the PR? |
3 tasks
@sarabala1979 |
JPZ13
pushed a commit
to pipekit/argo-workflows
that referenced
this issue
Jul 4, 2023
…CycleHook (argoproj#11113, argoproj#11117) (argoproj#11176) Signed-off-by: toyamagu2021@gmail.com <toyamagu2021@gmail.com>
jeremyhager
pushed a commit
to jeremyhager/argo-workflows
that referenced
this issue
Jul 7, 2023
…CycleHook (argoproj#11113, argoproj#11117) (argoproj#11176) Signed-off-by: toyamagu2021@gmail.com <toyamagu2021@gmail.com> Signed-off-by: Jeremy Hager <47301461+jeremyhager@users.noreply.github.com>
5 tasks
61 tasks
dpadhiar
pushed a commit
to dpadhiar/argo-workflows
that referenced
this issue
May 9, 2024
…CycleHook (argoproj#11113, argoproj#11117) (argoproj#11176) Signed-off-by: toyamagu2021@gmail.com <toyamagu2021@gmail.com> Signed-off-by: Dillen Padhiar <dillen_padhiar@intuit.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pre-requisites
:latest
What happened/what you expected to happen?
Description
Workflow is marked as completed before some templates triggered by LifecycleHook
Running
are marked as completed. And the node status never changed from Running.Workflow's Progress remains 1/2 permanently...
Consideration
I'm not sure, but I think the root cause is the logic of
executeWfLifeCycleHook
hook.expression
of Running Lifecycle Hook is"workflow.status == \"Running\""
, soargoexpr.EvalBool
returnsfalse
whenmain
template becomesworkflow.status=Succeeded
.hookNode
is not added tohookNodes
, thenexecuteWfLifeCycleHook
returnstrue
even if some nodes created by hook are in "Running" status.To confirm, I added the following code (obviously not good. only PoC) to the master branch, and seems like it works fine.
Version
latest
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: