Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Interruptible ignored when directly running tasks #6167

Open
2 tasks done
pimdh opened this issue Jan 14, 2025 · 0 comments
Open
2 tasks done

[BUG] Interruptible ignored when directly running tasks #6167

pimdh opened this issue Jan 14, 2025 · 0 comments
Labels
bug Something isn't working untriaged This issues has not yet been looked at by the Maintainers

Comments

@pimdh
Copy link

pimdh commented Jan 14, 2025

Describe the bug

Register the file below.

import time

from flytekit import task, workflow


@task(interruptible=True, retries=5)
def sleep_task() -> None:
    time.sleep(10)


@workflow
def sleep_wf() -> None:
    sleep_task()

Then if I run

pyflyte run -p scratch -d main remote-workflow sleep_wf

A pod is created which correctly includes the interruptible=true label, as well as the Spot node selector I configured. However, if I directly run the task with

pyflyte run -p scratch -d main remote-task sleep_task

Then the task is wrongly create with the interruptible=false label, and without the Spot node selector.

Note that also when directly executing the task, the task metadata indicate interruptible, even though the pod is not created as such:

{"tags":{},"cacheIgnoreInputVars":[],"runtime":{"type":"FLYTE_SDK","version":"1.14.3","flavor":"python"},"retries":{"retries":5},"interruptible":true}

Expected behavior

I expect both execution to be interruptible, but only the workflow execution creates an interruptible Pod, not the task execution.

Additional context to reproduce

Flyte core version 1.13.3
Flytekit version 1.14.3

Screenshots

No response

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes
@pimdh pimdh added bug Something isn't working untriaged This issues has not yet been looked at by the Maintainers labels Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working untriaged This issues has not yet been looked at by the Maintainers
Projects
Status: Backlog
Development

No branches or pull requests

1 participant