You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
go run ./cli --project-name=<PROJECT_ID> --image-name=<MY_IMAGE_NAME> --zone=europe-west4-a --gcs-path=gs://<BUCKET_FOR_LOGS> --disk-size-gb=50 --container-image=<MY_SOURCE_IMAGE> --timeout 100m
What I would expect?
I used the script successfully some weeks ago (on Sept 21) in the same region and it went smoothly. The output around that point was:
is misleading and most likely got distorted by Cloud Build from the original message from the VM creation which is of type:
ERROR: (gcloud.compute.instances.create) Could not fetch resource:
---
code: ZONE_RESOURCE_POOL_EXHAUSTED
errorDetails:
- help:
links:
- description: Troubleshooting documentation
url: https://cloud.google.com/compute/docs/resource-error
- localizedMessage:
locale: en-US
message: A e2-standard-2 VM instance is currently unavailable in the europe-west4-a
zone. 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: ''
vmType: e2-standard-2
zone: europe-west4-a
zonesAvailable: ''
reason: resource_availability
message: The zone 'projects/<PROEJCT_ID>/zones/europe-west4-a' does not have
enough resources available to fulfill the request. Try a different zone, or try
again later.
May I suggest that someone paid by Google propagates this to the Cloud Build team so that they can make sure that Cloud Build errors retain the original content of the VM error? That would help users understand what happens.
What happens?
The image-build script (both the go script and through
gcloud builds....
) fails with errorQuota 'CPUS_ALL_REGIONS' exceeded
:How to reproduce?
In a new project, create a bucket for logs
Enable services:
Add IAM policy bindings as instructed:
Add the bucket access:
Create the credentials with
and run the script:
What I would expect?
I used the script successfully some weeks ago (on Sept 21) in the same region and it went smoothly. The output around that point was:
It is not clear to me why the CPU limit would be an issue for this script.
Any suggestions on how to get this fixed?
Thank you!
The text was updated successfully, but these errors were encountered: