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_watch_timeout variable cannot be None #177

Open
cmhwang opened this issue Oct 31, 2023 · 3 comments
Open

job_watch_timeout variable cannot be None #177

cmhwang opened this issue Oct 31, 2023 · 3 comments
Assignees

Comments

@cmhwang
Copy link
Contributor

cmhwang commented Oct 31, 2023

Current behavior

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
@cmhwang cmhwang changed the title job_watch_timeout variable cannot be null job_watch_timeout variable cannot be None Oct 31, 2023
@jacobwhall jacobwhall self-assigned this Nov 1, 2023
@jacobwhall
Copy link
Member

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.

@cmhwang
Copy link
Contributor Author

cmhwang commented Nov 1, 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.

I'm on prefect version 2.14.0. I can look into if that's the cause of incompatibility

@jacobwhall
Copy link
Member

prefect version 2.14.0

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants