-
Notifications
You must be signed in to change notification settings - Fork 585
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
Clean up all task/job executions does not clean up tasks on unknown state #6110
Comments
Hello @juanpablo-santos , |
Hi, my bad, not an stacktrace but a warn message on log like
per task execution without its corresponding pod |
ouch, not exactly what I reported. Most executions get deleted. However, those executions that were unable to spin up a pod because of whatever reason (in our case, f.ex., a missing init container) are not deleted. Our first couple of executions pages look something like this: I'm so used to see it that thought that expected the Clean up to wipe it, and incorrectly thought that it wasn't deleting executions at all, but it is deleting executions with FAILED or SUCCESS state. Apologies on the noise, will update the issue title accordingly. |
Support option that will delete status of |
Description:
Not sure if bug or improvement request. Currently, the "Clean up all task/job executions" menu option at Tools section requires that the pods associated to the execution to be present at the cluster where te were run in order to remove the task execution from SCDF database.
In our case, our platform team runs a pipeline on every k8s cluster which wipes every pod that has been on finished/err state for more than 6 hours, so when we run the 'Clean up all task/job executions', every execution that hasn't its pod present on the cluster doesn't get deleted. The cleanup process tries to fetch the pod (to delete it, I presume), raises an exception that appears on the SCDF server logs, and then carries on and tries with the next execution.
Current workaround is to manually delete the rows at dabase level.
Release versions:
Custom apps:
N/A.
Steps to reproduce:
N/A.
Screenshots:
N/A.
Additional context:
N/A.
The text was updated successfully, but these errors were encountered: