Skip to content

[Bug]: FAILED_TO_START_DUE_TO_NO_CAPACITY  #1994

@judeleonard

Description

@judeleonard

Steps to reproduce

create a fleet.dstack.yml to provision remote backend from my on_prem server. This was created successfully.

dstack apply -f fleet.dstack.yml

type: fleet
name: model-dev-fleet

placement: any

# The user, private SSH key, and hostnames of the on-prem servers
ssh_config:
  user: my_user
  identity_file: ~/.ssh/id_rsa
  hosts:
    - 33.33.48.1

create another yml config to provision a development server with the provisioned fleet as the backend

dstack apply -f dev_environment.yml

type: dev-environment
name: model-dev-env

#python: "3.11"  
image: dstackai/base:py3.13-0.6-cuda-12.1

ide: vscode

spot_policy: auto

Actual behaviour

I got the below error

All provisioning attempts failed. This is likely due to cloud providers not having enough capacity. Check CLI and server logs for more details.

Then also tried to see extra details about the error with the below command

dstack ps --verbose

output below

NAME           BACKEND  REGION  INSTANCE  RESOURCES  SPOT  PRICE  STATUS  SUBMITTED   ERROR                                
 model-dev-env                                                     failed  54 sec ago  JOB_FAILED                           
                                                                                       (FAILED_TO_START_DUE_TO_NO_CAPACITY) 

Expected behaviour

Instance provisioning should be completed successfully with a vscode link to my workspace.

dstack version

0.18.22

Server logs

[12:45:55] INFO     dstack._internal.server.services.backends:404 Requesting instance offers from backends: []                                                                                              
[12:45:56] INFO     dstack._internal.server.background.tasks.process_runs:330 run(110058)model-dev-env: run status has changed SUBMITTED -> TERMINATING                                                     
           INFO     dstack._internal.server.services.jobs:283 job(0d49c8)model-dev-env-0-0: job status is FAILED, reason: FAILED_TO_START_DUE_TO_NO_CAPACITY                                                
[12:45:58] INFO     dstack._internal.server.services.runs:739 run(110058)model-dev-env: run status has changed TERMINATING -> FAILED, reason: JOB_FAILED

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions