Troubleshooting reservation creation

Stay organized with collections Save and categorize content based on your preferences.
This page shows you how to resolve issues with creating reservations of Compute Engine zonal resources.

In addition to the errors on this page, reservation creation can also fail due to issues that happen when creating Compute Engine resources. If your issue is not listed on this page, you might find the error by trying to create VMs with the resources that you want to reserve and reviewing the Troubleshooting VM creation page.

Reservation creation errors

If you can't create a reservation, it might be due to one of the errors in this section. If you can't create a shared reservation, also review Shared reservation creation errors.

Insufficient quota

A quota error occurs when a resource request exceeds your quota.

Error messages:

RESOURCE_NAME creation failed:
Quota QUOTA_NAME exceeded. Limit: QUOTA_LIMIT in region REGION
RESOURCE_NAME creation failed:
Quota QUOTA_NAME exceeded. Limit: QUOTA_LIMIT in zone ZONE

Resolution: Request a higher quota limit. For more information, see Requesting an increase in quota.

Resource availability

To create a reservation, all the resources you specify in the reservation must be available in order for them to be reserved for you.

Resource errors occur when you try to request new resources in a zone that cannot accommodate your request due to the current unavailability of a Compute Engine resource, such as GPUs or CPUs.

Resource errors only apply to new resource requests in the zone and do not affect existing resources. Resource errors are not related to your Compute Engine quota and only apply to the resource you specified in your request at the time you sent the request, not to all resources in the zone.

Error messages:

ZONE_RESOURCE_POOL_EXHAUSTED

ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS
The zone 'projects/PROJECT_ID/zones/ZONE' does not have enough resources available to fulfill the request.
Try a different zone, or try again later.
Resource exhausted (HTTP 429): QUOTA_EXCEEDED

Resolution:

  • Try to create the resources in another zone in the region or in another region.
  • Because this situation is temporary and can change frequently based on fluctuating demand, try your request again later.
  • Try to reduce the number of resources you are requesting. For example, it's usually easier to get a VM with less GPUs, disks, vCPUs, and/or memory. Additionally, if your request is for multiple VMs, it's easier to get a smaller number of VMs. A reduction in the number of resources you are requesting might let your request proceed.
  • Try to change the type of resources you are requesting. For example, it might be easier to get VMs with older CPU platforms. A change to the type resource you are requesting might let your request proceed.
  • To prevent this error, create Compute Engine reservations when the resources you need are available to reserve them within a zone. Reservations help ensure that resources are available whenever you need them, so keeping reservations of resources you need can help prevent this error.
  • If you are trying to create Spot VMs (or legacy preemptible VMs), remember that these VMs are spare capacity, which is unplanned and volatile, so they might not be obtainable at peak demand periods. Consequently, Spot VMs are only recommended for workloads with flexible time, location, and VM-configuration requirements. You can help prevent this error for Spot VMs by following the best practices to make your workload more flexible. If this error persists, use standard VMs instead.
  • If you were unable to resolve the error using any of the preceding instructions, try Getting support.

Zone availability

If you receive a notFound or does not exist in zone error when requesting new resources, it means that the zone you are requesting the resource in does not offer the resource or machine type that you have requested.

Error messages:

notFound

does not exist in zone

Resolution: See Regions and zones to find out which features are available in each zone.

Resource name

If you receive a resource already exists error when you try to create a resource, your creation request failed because you specified a non-unique name for the resource for the specified location and project.

Error messages:

The resource 'projects/PROJECT_NAME/zones/ZONE/RESOURCE_TYPE/RESOURCE_NAME' already exists"

The resource 'projects/PROJECT_NAME/regions/REGION/RESOURCE_TYPE/RESOURCE_NAME' already exists"

Resolution: Retry your creation request with a unique resource name.

Maximum VM count exceeded

The following error occurs when you try to create a reservation for more than 1000 VMs.

Error message:

Invalid value for field 'resource.specificReservation.count': VM_COUNT. Must be less than or equal to 1000
where VM_COUNT is the number of VMs in a reservation.

Resolution: Create multiple reservations with the same zone, project, and VM properties as this reservation, but reduce the number of VMs you want to reserve to up to 1000 VMs for each reservation.

Shared reservation creation errors

If you can't create a shared reservation, it might be due to one of the errors in this section or in Reservation creation errors.

Project without an organization

The following error occurs when you try to create a shared reservation in a project that does not belong to an organization.

Error message:

Cannot create Shared Reservations in a project that does not belong to an organization.

Resolution: Do one of the following:

Constraint violation

The following error occurs when the Shared Reservations Owner Projects (compute.sharedReservationsOwnerProjects) organization policy constraint does not allow a project to create and modify shared reservations.

Error message:

Constraint constraints/compute.sharedReservationsOwnerProjects violated for project projects/PROJECT_NUMBER
Shared reservation can not be created in this project for your organization.

Resolution: Do one of the following:

Invalid consumer projects

This section describes errors that occur when you specify invalid consumer projects for a shared reservation.

Project not found in this organization

The following error occurs when the consumer project you specified cannot be found in the same organization as the project you are currently using.

Error message:

Project PROJECT_ID doesn't exist or doesn't belong to the same organization of the current project.

where PROJECT_ID is a project ID that you specified as a consumer project.

Resolution: Do the following:

  1. View all the projects in the organization to verify that the specified consumer project exists in this organization.
  2. View the project to verify that you specified its project ID, PROJECT_ID, correctly.

Owner project specified as a consumer project

The following error occurs when you try to specify a shared reservation's owner project (the project used to create the shared reservation) as a consumer project.

Error message:

Project PROJECT_ID which is the owner project of this reservation is always included in the share projects, please do not add it.

Resolution: Remove the owner project from the list of consumer projects. A shared reservation can always be consumed by VMs in the owner project, so you cannot include it in the list of consumer projects.

Zero consumer projects

The following error occurs when a shared reservation has zero consumer projects:

Error message:

Have to share with at least 1 project.

Resolution: Do one of the following:

Maximum consumer projects exceeded

The following error occurs when a shared reservation has more than 100 consumer projects:

Error message:

Can only share with at most 100 projects.

Resolution: Do the following:

  1. Reduce the number of consumer projects to, at most, 100 consumer projects for the shared reservation.
  2. If you still need to reserve capacity for any omitted projects, create another shared reservation that is shared with those projects.

Maximum shared reservation count exceeded

The following error occurs when your organization already has 100 shared reservations with the same VM properties.

Error message:

Cannot support more than 100 shared reservations of the same shape under an organization.

Resolution: Follow the best practice of minimizing the number of separate shared reservations with the same VM properties in your organization by doing the following:

  • Resize existing reservations to have larger VM counts. If you have multiple identical shared reservations that do not exceed the maximum VM count, then consider if you can combine them into fewer shared reservations with the same combined VM count.
  • Modify the consumer projects for a shared reservation to include more projects. For example, if you have multiple shared reservations with the same VM properties and zone but similar owner and consumer projects, consider if you can combine them into one shared reservation that can be consumed by all of these projects.
  • Delete shared reservations that you no longer need.