You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the develop-k8s branch attempting to deploy a prefect flow using kubernetes results in the error below:
pydantic.error_wrappers.ValidationError: 1 validation error for KubernetesJob
job_watch_timeout_seconds
none is not an allowed value (type=type_error.none.not_allowed)
It seems like there is some kind of update or prefect bug requiring that job_watch_timeout_seconds can't be set to None in the geodata-k8s block in prefect.
Tasks
Look into if there's any way to set a None or max value here
look into whether this is a bug or an updated requirement
The text was updated successfully, but these errors were encountered:
cmhwang
changed the title
job_watch_timeout variable cannot be null
job_watch_timeout variable cannot be None
Oct 31, 2023
Hey @cmhwang, I attempted to replicate this error on my own machine today, and didn't run into this issue. What version of Prefect are you using? Perhaps updating to a later version will resolve this problem.
Hey @cmhwang, I attempted to replicate this error on my own machine today, and didn't run into this issue. What version of Prefect are you using? Perhaps updating to a later version will resolve this problem.
I'm on prefect version 2.14.0. I can look into if that's the cause of incompatibility
That's a pretty recent version, so that's probably not causing the issue. I'm working on switching from Prefect agents to workers, which will overwrite a lot of the relevant code. Once I push those changes, let's try again and see if you're still encountering this bug.
Current behavior
In the develop-k8s branch attempting to deploy a prefect flow using kubernetes results in the error below:
It seems like there is some kind of update or prefect bug requiring that job_watch_timeout_seconds can't be set to None in the geodata-k8s block in prefect.
Tasks
The text was updated successfully, but these errors were encountered: