Hello, a few of our flow runs failures from 4:30 to 4:50 PST time with the same issue of failure in ...

Hui Zheng

01/21/2021, 1:15 AM

Hello, a few of our flow runs failures from 4:30 to 4:50 PST time with the same issue of failure in retrieving task

GCS_result

. It happened to flow runs on different agents and k8e clusters. I wonder if there is a Prefect-cloud infrastructure issue?

Hui Zheng

01/21/2021, 1:16 AM

Below are the failed flow runs https://cloud.prefect.io/semios/flow-run/8df7da62-f3b9-4b38-8773-03aefbfac736 https://cloud.prefect.io/semios/flow-run/b4a799a6-b502-4649-b522-64cb9f1ba2c7 https://cloud.prefect.io/semios/flow-run/86cc4e77-84c4-42f4-8a1a-c805600d98da

Hui Zheng

01/21/2021, 1:20 AM

below is the log from one of the run

logs (1).txt

Chris White

01/21/2021, 4:43 AM

Hi @Hui Zheng - this isn’t related to Prefect Cloud; the error I see is

Copy code

AttributeError("'Blob' object has no attribute 'download_as_bytes'")

which I believe is related to your local version of `google-cloud-storage`; here’s a relevant issue: https://github.com/PrefectHQ/prefect/issues/3870 and a corresponding PR that addresses it: https://github.com/PrefectHQ/prefect/pull/3875. The fix for this was released with 0.14.1. All that being said, you can resolve this in one of two ways (whichever is more convenient for you): • upgrade your version of

google-cloud-storage

in your Flow’s docker image • upgrade your Flow’s version of Prefect to 0.14.1

Hui Zheng

02/09/2021, 8:09 PM

Thank you, Chris. !

👍 1

3 Views

Open in Slack

Previous Next

Prefect Community

Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.