Skip to content

Detect Vast.ai interruptions during provisioning #4037

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.

Sign up for GitHub

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

Merged
jvstme merged 1 commit into from
Jul 16, 2026
Merged

Detect Vast.ai interruptions during provisioning #4037

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions src/dstack/_internal/core/backends/vastai/compute.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -205,6 +205,16 @@ def update_provisioning_data(
and ": OCI runtime create failed:" in resp["status_msg"]
):
raise ProvisioningError(resp["status_msg"])
if (
resp.get("cur_state")
== resp.get("intended_status")
== resp.get("next_state")
== "stopped"
):
# Can happen, among other cases, when a spot instance is outbid (interrupted)
raise ProvisioningError(
"Vast.ai reports current and intended instance state as `stopped`"
)


class VastAIOfferBackendData(CoreModel):
Expand Down
Loading