<#310 Transition to failed state if the task canno...
# flyte-github
a
#310 Transition to failed state if the task cannot be created Pull request opened by pingsutw Fixes flyteorg/flyte#3281 TL;DR Transition to failed state if the task isn't created. otherwise, the task will run forever. 1 round (phase:
PhaseNotStarted
) • Webapi plugin try to allocate token 2 round (state:
PhaseAllocationTokenAcquired
, phase:
queued
): • Plugin fail to create a task, and will not update the task state. The state is
PhaseAllocationTokenAcquired
in this round • Task handler send the task event (queued) to admin • However we transition the phase from queued to running here • And we will record the node event (running) in the node executor 3 round (state:
PhaseAllocationTokenAcquired
, phase:
running
): • Will try to create a task, and fail again • In the screenshot below, you can see the node phase is
running
, but the task state is
queued
4+ round • Repeat 3 round Type ☑︎ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☑︎ Code completed ☑︎ Smoke tested ☑︎ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description Before

image▾

After

image▾

Tracking Issue flyteorg/flyte#3281 It's related to this issue propeller panic because taskCtx.ResourceMeta() is nil. However, it should never happen. it was happening because we tried to abort the task that doesn't exist. Follow-up issue NA flyteorg/flyteplugins ✅ All checks have passed 6/6 successful checks