In kubernetes-sigs/dra-driver-nvidia-gpus repo, CI job for pull-dra-driver-nvidia-gpu-e2e-gcp-nvkind is failing with the following error:
ERROR: (gcloud.compute.instances.create) Could not fetch resource:
---
code: ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS
errorDetails:
- help:
links:
- description: Troubleshooting documentation
url: https://cloud.google.com/compute/docs/resource-error
- localizedMessage:
locale: en-US
message: A n1-standard-4 VM instance with 1 nvidia-tesla-t4 accelerator(s) is
currently unavailable in the us-central1-b zone. Consider trying your request
in the us-central1-a, us-central1-f zone(s), which currently has capacity to
accommodate your request. Alternatively, you can try your request again with
a different VM hardware configuration or at a later time. For more information,
see the troubleshooting documentation.
- errorInfo:
domain: compute.googleapis.com
metadatas:
attachment: nvidia-tesla-t4:1
vmType: n1-standard-4
zone: us-central1-b
zonesAvailable: us-central1-a,us-central1-f
reason: resource_availability
message: The zone 'projects/k8s-infra-e2e-boskos-gpu-06/zones/us-central1-b' does
not have enough resources available to fulfill the request. 'NULL:0/NULL:0/NULL:0
(state:STOCKOUT, sub-state:STOCKOUT, resource type:compute)'.
Eg: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_dra-driver-nvidia-gpu/1336/pull-dra-driver-nvidia-gpu-e2e-gcp-nvkind/2087653433828970496
Can I get some help on this?
- Is this a temporary issue with
us-central1-b zone? If so, when can I expect a resolution?
- OR is
us-central1-b no longer supporting the n1-standard-4 instance? Should I be switching over to a or f?
What's the recommended action if we see such issues in the future?
In kubernetes-sigs/dra-driver-nvidia-gpus repo, CI job for
pull-dra-driver-nvidia-gpu-e2e-gcp-nvkindis failing with the following error:Eg: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_dra-driver-nvidia-gpu/1336/pull-dra-driver-nvidia-gpu-e2e-gcp-nvkind/2087653433828970496
Can I get some help on this?
us-central1-bzone? If so, when can I expect a resolution?us-central1-bno longer supporting then1-standard-4instance? Should I be switching over toaorf?What's the recommended action if we see such issues in the future?