https://prefect.io logo
Title
q

quassy

12/15/2022, 10:44 AM
Hey! In the release notes to 2.7.1:
improved timeout handling on the
KubernetesJob
block - this timeout is now disabled by default (i.e.
job_watch_timeout_seconds
is set to
None
)
When I now try to run a pipeline without having that parameter explicitly set to a not-None value in KubernetesJob(...), I get this error from Prefect Cloud.
Submission failed. 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)
Is this intended?
m

Mason Menges

12/15/2022, 9:06 PM
Hmm, I wouldn't think this is intended since it should be defaulting to None if you don't specify it, if you can put together a reproducible example including the block configuration and prefect version running on your cluster it may be worth opening a bug on our repo for this.
q

quassy

12/15/2022, 10:37 PM
@Mason Menges It is defaulting to None but apparently None is not accepted by Prefect Cloud or the default runner image (not really sure who is throwing the error). I have created an issue, do you need any other info to reproduce? https://github.com/PrefectHQ/prefect/issues/7911