Skip to content

[Bug]: Instances shown as Failed in Verda are Provisioning in dstack #3746

Closed

Description

@r4victor

Steps to reproduce

  1. Provision many Verda instances so that some of them are failed due to no capacity, e.g.
type: fleet
name: test-verda-fleet
nodes:
  min: 0
  target: 30
backends: [verda]
resources:
   cpu: 1..
   memory: 1GB..
   gpu: 0
placement: any
spot_policy: on-demand
  1. Even if some instance are failed in Verda they are still Provisioning in dstack which means the fleet and instances stay in Provisioning until the provisioning timeout is due (minutes=10)

Actual behaviour

Not confirmed but possible consequence of #3723

Expected behaviour

update_provisionig_data() fails the instance by raising ProvisioningError when the instance in failed or terminated in the provider.

dstack version

master

Server logs

Additional information

No response

Activity

  1. self-assigned this
    on Apr 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions