Hi, I'm receiving the following error when running...
# prefect-cloud
l
Hi, I'm receiving the following error when running my flow using a Azure Push Pool. This push pool was still working last Friday. Does anyone know how I can solve this issue? Or is this a bug on the Prefect Cloud side?
j
hey, are you able to share the full error from the logs?
l
Where can I find the full logs? This happens seconds after I start the run, which means the Azure container is not yet created, and therefore no container logs are available. From Prefect Cloud I'm only able to extract this log, also when setting the PREFECT_LOGGING_LEVEL to DEBUG. What's interesting is that when executing the flow again I receive slightly different error messages: • Failed due to a
ValueError
caused by too many values to unpack, likely in the context of generating a job configuration in Prefect Cloud • Failed due to a
ValueError
in Prefect flow `push_work_pool`: Failed to generate job configuration: too many values to unpack (expected 2) When running this flow using a local work pool the flow works fine so it has to do something with my Azure container push workpool
j
Could you share your workspace id and a flow run id with this error and I can take a look? It sounds like a work pool field is maybe given the wrong type, although I would have expected a clearer error message.
l
Sure, my workspace ID is 2bdaaaa4-4e5e-4ebe-b968-ce30f5e9ef52, and the flow run id 40af5fcb-4867-4809-8210-f36b504ee563
j
thanks for sharing those. This looks like this is potentially an issue on our end. Some of your env vars are bet set using nested fields (multiple `.`'s in the path) from blocks (which should absolute work). You may be able to remove those temporarily as workaround but let me see if I can get a fix released shortly!
l
Good to know, and thanks for your help! Could you let me know when this fix is released?
👍 1
j
hey sorry for the delay here! This should be released if you could give it another go?
l
Hi Jake, I just tested it and it works now, thanks for helping me out!
j
great to hear! thanks again for flagging the issue!