-
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 hangs after clicking stop and terminate #10491
Comments
Grain.Highlight.7vm9f15b0ukV93KlO59k6kH8m8eTMiPiwxysYezG.mp4The above video demonstrates what we're seeing along with the controller logs. It doesn't look like there's any logging output unfortunately |
On a call with @juliev0 - we need the Argo Server logs to get more clarity into what's happening @tico24 or any others, if you see this happen again, can you post the Argo Server logs as well? Also, if we're seeing any logs being sent from the main or wait container that can inform us whether the SIGINT or SIGTERM signals are going out, that would be super helpful as well |
Naturally, every workflow I've tried to stop today just stops gracefully. I'll add logs as soon as I can recreate. |
…10491 (#10639) Signed-off-by: Isitha Subasinghe <[email protected]>
…10491 (#10639) Signed-off-by: Isitha Subasinghe <[email protected]>
Pre-requisites
:latest
What happened/what you expected to happen?
When clicking stop or terminate within the UI, we are noticing that workflows are left hanging in a running state. The only way to get them to actually stop is to delete the workflow. This causes a problem for users who want to stop the workflow but keep the record in their archives
Here's a list of some other issues that I think might be related. I will keep this list up to date as more arise:
emissary
executor forcing the workflow to hang in "Running" state #8680Pod was active on the node longer than the specified deadline
-remain in status Running #9934Version
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.
Unfortunately, this happens intermittently. I will update this issue with some videos and see if I can find some workflows that consistently trigger it using only public images
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: