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

Job stuck in Cancelling state #16001

Open
hpapazov opened this issue Nov 13, 2024 · 1 comment
Open

Job stuck in Cancelling state #16001

hpapazov opened this issue Nov 13, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@hpapazov
Copy link

Bug summary

While testing Prefect Worker with prefect-kubernetes 0.5.3, I observed a change in how the package handles job Cancellation. Once you cancel the job via the UI, the job gets stuck in Cancelling state and never transitions to Cancelled state. I tested the same steps with prefect-kubernetes 0.5.0 and I did not observed the above behavior. The job transiting from Cancelling to Cancelled state.

Version info

Prefect packages used when job gets stuck in Cancelling state:
- prefect-client==3.0.4
- prefect-kubernetes==0.5.3


Prefect packages used when job transitions to Cancelled state:
- prefect-client==3.0.4
- prefect-kubernetes==0.5.0

Additional context

To reproduce the issue:

  1. Start a job
  2. Cancel vi UI
  3. Observe the job status remaining "Cancelling" and not transitioning to "Cancelled"

Logs for a job running against prefect-kubernetes==0.5.3 that gets stuck in Cancelling state

image

Logs for a job running against prefect-kubernetes==0.5.0 that gets transitioned to Cancelled sate

image

@hpapazov hpapazov added the bug Something isn't working label Nov 13, 2024
@haddon-korinek-ent
Copy link

Also ran into this recently and saw it was deprecated here: #14611

The recommended approach now is to execute your remote flow runs using a Runner instead of calling the engine entrypoint directly.

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
None yet
Development

No branches or pull requests

2 participants