https://prefect.io
Join Slack
<@U01AGSHH6UR>, <@U01DJDK6AQ7> - any other ideas on why flows might not execute that isnt a labeling...
# ask-community
s
@Greg Roche, @Amanda Wee - any other ideas on why flows might not execute that isnt a labeling issue? Now using an S3 bucket, I can confirm that the only label on a flow is “any”. There is an agent running and polling which has “any” label set. And yet the agent is always saying “No flow runs found”. Im pulling my hair out trying to get the hello world equivalent running here and I just dont understand where things might be going wrong :s
@Sean Talia - responding here to now interrupt Karolinas thread if youre able to lend some thoughts. Using the server not the cloud. Definitely no hidden labels
s
okay are you also running a 
LocalRun
RunConfig like @Karolína Bzdušek is?
i'm no expert, but if that's the case, I think it's conceivable that a 
DockerAgent
will not even try to pull work off the queue if the flow hasn't been configured with a 
DockerRun
config, even if the label set seems to match
s
Ive tried it locally and with the two dask executors - its the hello_flow example. If the agent is launched in my terminal, it works, but if I launch a local agent or a docker agent they will both start and connect to the apollo:4200 api, but neither of them will get any flows to execute
s
okay yeah so just from looking at the code you have here, you're not specifying anything for your 
run_config
option for your flow, so it's going to default to using the 
LocalRun
, which means that you have a mismatch between your run config option and your agent type
can you try to spin up an agent with exactly the same parameters except do 
prefect agent local start
instead of 
prefect agent docker start
(or however you're launching your agent)?
s
Yeah I now both a local and a docker agent in the docker-compose file, and one flow for LocalRun and one with DockerRun. Alas, no flows are picking up anything still.
The super weird part is if I run 
prefect agent local start
in my terminal, it will work. The flows will start being run instantly. But if I take the same command and put it inside the docker-compose which has the apollo service and everything, it talks to the server just fine, it just never gets given any flows to run!
s
huh interesting okay, i've never tried to launch an agent from within a container, i also only do so from a virtualenv on my laptop and have never had this issue (except for label / runconfig mismatches)
s
Yeah, its super odd, I wish I could just open up the agents to see what difference there is under the hood from my terminal and inside docker. Might call in the big guns with @josh and @Zanie if youre around somewhere 🙂
s
i don't know enough about how exactly the agents pick up work that the server has queued up to debug this much further, it's definitely odd to me that the agent is communicating just fine with the server but not picking up a scheduled run
sorry for being useless! i'd love to see what the answer is here though 😎
s
I too find it odd. Im trying to sell Prefect over airflow 2.0 in a meeting tomorrow but so far cant even get the hello world example running in our environment, so fingers crossed something makes sense soon. Thanks for the assist!
Open in Slack
PreviousNext
Powered by

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.

Powered by