Hi Im observing dynamic tasks stuck in Queued state on EKS d

Question

Hi Im observing dynamic tasks stuck in Queued state on EKS deployment I also see Parallelism 0 which might be the cause because the base dynamic task is Running and then any spawned tasks are not able to run since Parallelism=0 How do I set it in `flyte core` Helm deployment Don t see a a field for it in values here Or should I set it somewhere else <https github com flyteorg flyte blob master charts flyte core values yaml>

Yee · Answer

i don t think that should matter 0 parallelism should mean no limit

Yee · Answer

it s probably stuck for other reasons

Yee · Answer

are the pods created

Yee · Answer

describe the pods if they are check propeller logs and grep for execution id if not

Geert · Answer

Thanks < Yee> Pods were not created and I found some errors in the flytepropeller logs `service flyte binary webhook not found`

Geert · Answer

Im using `flyte core` not `flyte binary` also in none of the configmaps I can find something about `flyte binary` `k describe cm n flyte | grep binary` is empty

Geert · Answer

Why is it looking for this service and how do I point it somewhere else

Geert · Answer

I do have `flyte pod webhook` Service

Geert · Answer

Its strange because it references both `flyte pod webhook` and `flyte binary webhook` ```RuntimeExecutionError failed during plugin execution caused by failed to execute handle for plugin container InternalError failed to create resource caused by Internal error occurred failed calling webhook failed to call webhook Post service flyte binary webhook not found```

Geert · Answer

In flytepropeller configmap ```webhook certDir etc webhook certs serviceName flyte pod webhook```

Yee · Answer

the webhook is needed for some things yes does your task have secrets

Geert · Answer

Yeah it does but why is it looking for binary

Geert · Answer

When I m using flyte core

Geert · Answer

< Yee> Found the cause there was a leftover mutating webhook in the cluster from a previous test with `flyte binary` so even though we didn t have any references to `flyte binary` in our current setup this mutating webhook was still triggering However there was no Service to back it hence the error and tasks stuck in Queued state The fix ```kubectl delete flyte binary webhook```

Yee · Answer

ah nice

Yee · Answer

thanks