When subworkflows/tasks are not run because the ex...
# ask-the-community
f
When subworkflows/tasks are not run because the exceed the resource quota, shouldn't they automatically start running once enough resources are available again or the limits were increased? Right now the tasks stay in running, but nothing happens...
y
yes. they should. do you see that not happening?
that issue isn’t entirely related right?
that bug is an admin bug… when it creates the pod, admin isn’t respecting the project/domain level setting, but is creating the pod with the base Admin settings instead
but once the Pod is created, with whatever resources it’s created with, that behavior should take over
f
I updated the cluster-resource via flytectl first, that didn't work as per the bug. I then increased the defaults in the my helm chart values and updated that, which restarted flyteadmin, then they correctly were launched automatically
Didn't see that at first, because in console it all shows as running, and only in the details you see that the actual status is queued or so
y
got it, yeah the statuses are a bit misleading
thanks
f
Any plans to improve that as well? The correct information seems to be there....
y
reporting and observability is definitely a topic high on the list in general. mind filing an issue for it though with some screenshots if you see it again?
f
sure
Not quite the same as the exceeded resource quota, but the more common queued: https://github.com/flyteorg/flyte/issues/3211
y
thank you!
101 Views