-
Notifications
You must be signed in to change notification settings - Fork 672
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
[BUG] MapTasks don't cleanup pods when aborting an execution #5222
Comments
To address the issue where pods remain in a Here are specific steps to troubleshoot and potentially resolve the issue:
If these steps do not resolve the issue, providing detailed logs and steps to reproduce can help further diagnose the problem. There have been no recent changes in the Flyte codebase specifically related to the Sources
|
So we've spent some more time investigating and we believe it's a bit more complex than just removing the finalizers so I have closed the #5221. From our current investigations we've found that when
The pluginState
We saw that the value was able to be fetched from the
|
We've recently upgraded to 1.13.1 and haven't seen this issue popping up. Closing. |
Describe the bug
When a workflow is triggered with map tasks and then cleaned up, pods are deleted but the finalizer never removed so pods stay in
Terminating
StateExpected behavior
Propeller should not only delete the pod but also cleanup the finalizer so pod are properly removed.
Additional context to reproduce
Create a Workflow with a MapTask with many items, abort execution and check the pods in the kubernetes namespace
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: