Recently Upgraded prefect from 2 9 0 to 2 10 1 Everything wa

Question

Recently Upgraded prefect from 2 9 0 to 2 10 1 Everything was working fine before with 2 9 0 but now getting error lt FileNotFoundError Errno 2 No such file or directory opt prefect src downloader 0 8 py gt The code is stored in the root directory Using docker container Code stored on minio bucket

Zanie · Answer

Hm 2 10 1 is ~2 lines of code different than 2 10 0 and I don t think it would cause that error

Zanie · Answer

Can you share a traceback

Faheem Khan · Answer

sorry my bad it s 2 9 0 to 2 10 1 I have updated my question

Chris White · Answer

Could you share your deployment configuration specifically your storage block setup

Faheem Khan · Answer

`prefect deployment build src downloader 0 8 py main downloader name downloader 0 8 tag dev work queue q1 output deployments downloader 0 8 yaml sb remote file system minio1 ib docker container docker custom image` `prefect deployment apply deployments downloader 0 8 yaml`

Faheem Khan · Answer

Note code py is referring to downloader 0 8 py

Faheem Khan · Answer

`name downloader 0 8` `description null` `version 94d93d577332f48f00736e5e7c038598` ` The work queue that will handle this deployment s runs` `work queue name q1` `work pool name default agent pool` `tags ` ` dev` `parameters ` `schedule null` `is schedule active true` `infra overrides ` ` ` ` DO NOT EDIT BELOW THIS LINE` ` ` `flow name Main downloader` `manifest path null` `infrastructure ` `type docker container` `env ` `labels ` `name null` `command null` `image prefect2` `image pull policy NEVER` `image registry null` `networks ` ` prefect server` `network mode null` `auto remove true` `volumes ` ` home dev projects SDA Rail 0 4 flows flows` ` home dev Sharedstorage mnt logs data source logs` `stream output true` `memswap limit null` `mem limit null` `privileged false` ` block document id edbdb1ba 1d3e 4c14 b70a f57fb0a3794b` ` block document name docker custom image` ` is anonymous false` `block type slug docker container` ` block type slug docker container` `storage ` `basepath ` `settings ` `use ssl false` `key abc` `secret abc` `client kwargs ` `endpoint url ` ` block document id 09f7e8f0 dc8a 4f03 86c1 f837b5bc8384` ` block document name minio1` ` is anonymous false` `block type slug remote file system` ` block type slug remote file system` `path ` `entrypoint src downloader 0 8 py main downloader` `parameter openapi schema ` `title Parameters` `type object` `properties ` `required null` `definitions null` `timestamp 2023 04 07T03 53 07 772296+00 00 `

Chris White · Answer

There are no references to `code py` in your `deployment yaml` so I don t think this is coming from within Prefect s engine

Faheem Khan · Answer

I have edited the original question please check the screen snaps as well

Faheem Khan · Answer

Whole error log

Faheem Khan · Answer

Same error for other flow

Chris White · Answer

What exactly did you upgrade from 2 9 to 2 10 1 was it your agent your local environment the prefect installation within your docker image or some combination

Chris White · Answer

None of this logic should be different though between versions so I m not totally sure what could be causing this

Faheem Khan · Answer

I am running prefect in docker contailers prefect server and agent both are running in separate docker containers using the same official prefect image which I have customized

Faheem Khan · Answer

I think there must be some kind of bug as instead of looking for the code in src downloader 0 8 py prefect is looking for the code in opt prefect src downloader 0 8 py

Faheem Khan · Answer

The code location is clearly defined in the deployment configuration and also the same location src downloader 0 8 py on minio storage

Chris White · Answer

So I m guessing your Docker image is the one you upgraded Can you confirm that downgrading prefect within the image resolves the issue

Chris White · Answer

Assuming that s the case could you open an issue for this I can investigate tomorrow

Faheem Khan · Answer

I redownloaded the prefect image 2 10 1 and customized it instead of upgrading my old image Anyway I will roll back to prefect 2 9 0 until this issue is resolved

Chris White · Answer

< Faheem Khan> this issue should now be fixed in 2 10 2

Faheem Khan · Answer

Thanks confirmed it s running without any issue