Skip to content
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

GCP Batch Task Runner did not send delete signal to two completed jobs #4281

Closed
japerry911 opened this issue Jul 8, 2024 · 1 comment
Closed
Labels
bug Something isn't working

Comments

@japerry911
Copy link

Describe the issue

Hello team,

We are potentially having an issue.

These 2 batch jobs finished about 10-20 minutes ago, and they aren't deleting/moving on to next step in Kestra. This is the first time I encountered this. I am letting it still run in case it deletes them.

  • I don't see anything in GCP logger indicating a delete failed or was requested.

Screenshot 2024-07-08 at 9 26 55 AM
Screenshot 2024-07-08 at 9 26 45 AM

There was also no logs within Kestra stating that Jobs were deleted. Lastly, they did not delete even when killed even though that works with new update.

This might be a one off case, but thought it was worth reporting, let me know if you need anymore details. Thanks

Environment

  • Kestra Version: 0.17.11
  • Operating System (OS/Docker/Kubernetes): Kestra Cloud
  • Java Version (if you don't run kestra in Docker): n/a
@japerry911 japerry911 added the bug Something isn't working label Jul 8, 2024
@japerry911
Copy link
Author

Closing as I cannot reproduce this and have ran a few long executions since, that delete successfully. Thinking this is one off.

@japerry911 japerry911 closed this as not planned Won't fix, can't repro, duplicate, stale Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

1 participant