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
Daemon pods keep running after workflow DAG fails when using failFast: true #10313
Open
2 of 3 tasks
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
shuangkun
added a commit
to shuangkun/argo-workflows
that referenced
this issue
Apr 2, 2024
…enabled. Fixes:argoproj#10313 Signed-off-by: shuangkun <[email protected]>
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?
I expect the daemon pod to be terminated when the workflow fails, but that's not the case. The workflow is correctly marked as failed but the daemon pod keeps running until the workflow is deleted. I think it tries to delete the daemon, but it's getting a 404 response (from controller):
Some other notes:
failFast
the daemon pod is properly deletedwithParams
, the daemon pod is not properly deleted if it fails.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: