Trying to upgrade from 0 10 7 to 0 11 worked through a few i

Question

Trying to upgrade from 0 10 7 to 0 11 worked through a few issues but have been banging my head for awhile trying to figure out what I m doing wrong here Flow Runs with newly registered flow version fail immediately with Failed to load and execute Flow s environment AttributeError KubernetesJobEnvironment object has no attribute unique job name On closer inspection Cloud UI still shows Prefect Core Version 0 10 7 for the flow I m using new docker base image FROM prefecthq prefect 0 11 5 python3 8 and updated ``` python dependencies= kubernetes docker prefect gcp prefect kubernetes + prefect gcp ~=0 11 + prefect kubernetes ~=0 11 ``` this may be redundant I can see in the output from the register build process ```Step 1 36 FROM prefecthq prefect 0 11 5 python3 8 Step 30 36 RUN pip show prefect || pip install git+<https github com PrefectHQ prefect git 0 10 7 egg=prefect kubernetes > gt Running in e3773eba79d4 Name prefect Version 0 11 5 ``` Additionally I have pulled and run the docker image from the registered flow and inside ```root b3fc72e3e101 python Python 3 8 3 default May 20 2020 20 38 46 GCC 8 3 0 on linux Type help copyright credits or license for more information gt gt gt import prefect pr gt gt gt prefect version 0 11 5 ``` I ve now even deleted the flow all past versions and registered again and still seeing Prefect Core Version 0 10 7 in Cloud UI what am I missing doing wrong

Dan DiPasquo · Answer

I ve also explicitly added ``` flow storage = Docker + prefect version= 0 11 5 ``` still no joy I m afraid

Dan DiPasquo · Answer

ooooo I suspect that the agents need to be updated too it s late talking out loud here

Dan DiPasquo · Answer

Well darn really thought that would be it but have upgraded agent to 0 11 5 now too and flow run still fails with 4 Jun 2020 11 30pm Failed to load and execute Flow s environment AttributeError KubernetesJobEnvironment object has no attribute unique job name

Dan DiPasquo · Answer

OK well all that and I finally found that my local venv in which I was running flow register was rebuild to 0 10 7 Upgrading that and re registering flow now shows Prefect Core Version 0 11 5 and the flow runs It fails for different reason but at least it runs and and I can keep working through those Sheesh I ll leave this thread here on the chance my stumbling through this might spare someone else and or enjoy a laugh at my expense

Jenny · Answer

Thanks for sharing < Dan DiPasquo> hope this helps others in the future