Can't start a pod anymore with graphql mutation without a networkVolumeId

When I run this mutation
mutation podFindAndDeployOnDemand($input: PodFindAndDeployOnDemandInput) {
  podFindAndDeployOnDemand(input: $input) {
    id
    imageName
    env
    machineId
    ports
    machine {
      podHostId
    }
  }
}
with these inputs

{
    "input": {
        "cloudType": "SECURE",
        "name": "****",
        "templateId": "*****",
        "env": [
            { "key": "USERNAME", "value": "*****" },
            { "key": "TYPE", "value": "****" },
            { "key": "POD_NAME", "value": "******" }
        ],
        "gpuCount": 1,
        "gpuTypeId": "NVIDIA A40"
    }
}


I get the following error

{
    "errors": [
        {
            "message": "There are no longer any instances available with enough disk space.",
            "path": [
                "podFindAndDeployOnDemand"
            ],
            "extensions": {
                "code": "RUNPOD"
            }
        }
    ],
    "data": {
        "podFindAndDeployOnDemand": null
    }
}


This is very new it wasn't happening before, are we forced to use networkVolumeIds now?
Was this page helpful?