This document explains how to resolve issues with creating reservations. Tolearn more about reservations, seeAbout reservations.

In addition to the errors on this page, reservation creation can also fail dueto issues that happen when creating Compute Engine resources. If yourissue is not listed on this page, then do the following:

1. Create VMs with theresources that you want to reserve.

2. If you still encounter errors, then seeTroubleshooting VM creation.

Reservation creation errors

If you can't create a reservation, then it might be due to one of the errorsin this section. If you can't create a shared reservation, then also reviewShared reservation creation errors inthis document.

Insufficient quota

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

Error messages:

RESOURCE_NAME creation failed:QuotaQUOTA_NAME exceeded. Limit:QUOTA_LIMIT in regionREGION

RESOURCE_NAME creation failed:QuotaQUOTA_NAME exceeded. Limit:QUOTA_LIMIT in zoneZONE

Resource exhausted (HTTP 429): QUOTA_EXCEEDED

Resolution: Request a higher quota limit. For more information, seeEdit your quota.

Resource availability

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

The following are examples of common resource errors that you might encounterwhen you request new Compute Engine resources or create new reservations:

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.

AVM_TYPE_AND_SIZE VM instance withRESOURCE_ATTACHMENT is currently unavailable in theZONE zone.Capacity changes frequently, so try your request in a different zone, with a different VM hardwareconfiguration, or at a later time. For more options, see troubleshooting documentation.

AVM_TYPE_AND_SIZE VM instance withRESOURCE_ATTACHMENT is currently unavailable in theZONE zone, because ofREASON.Consider trying your request in theZONE zone(s), which currently has capacity to accommodate your request.If you cannot move your VM toZONE, review theREASON failure resolution instructions available in troubleshooting documentation, then try your request again.If your workload can't accommodate the suggested resolution, try your request with a different VM hardware configuration or at a later time.

To learn how to resolve resource errors, seeTroubleshooting resource availability errors.

Zone availability

If you receive anotFound ordoes not exist in zone error whenrequesting new resources, it means that the zone you are requesting the resourcein does not offer the resource or machine type that you have requested.

Error messages:

notFound

does not exist in zone

Resolution: SeeRegions and zones to findout which features are available in each zone.

Resource name

If you receive aresource already exists error when you try to create aresource, your creation request failed because you specified a non-uniquename 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 aunique resource name.

Maximum VM count exceeded

The following error occurs when you try to reserve more VMs than are allowed ina reservation.

Error message:

Invalid value for field 'resource.specificReservation.count':VM_COUNT. Must be less than or equal to 1000

Resolution: Create multiple reservations that specify the same zone,project, and VM properties. However, ensure that each reservation doesn'treserve more than the following number of VMs:

• If you specify a compact placement policy with a maximum distance value of2 in the reservation, then you can reserve up to thesupported number of VMs.

• Otherwise, up to 1,000 VMs.

Shared reservation creation errors

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

Project without an organization

The following error occurs when you try to create a shared reservationin 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:

• Migrate this project to an organizationbefore using it to create a shared reservation.
• Create a shared reservation using a project that belongs to anorganization.

Constraint violation

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

Error message:

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

Resolution: Do one of the following:

• Use a project that is allowed to create and modify sharedreservations. To see which projects in your organization have this permission,view the shared reservations organization policy constraint.
• Grant the project permission to create and modify shared reservations byediting the shared reservations organization policy constraint.If you continue to see this error after editing, then you might just need towait a few minutes for the edit to take effect.

Invalid consumer projects

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

Project not found in this organization

The following error occurs when the consumer project you specified can't befound in the same organization as the project you're using.

Error message:

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

WherePROJECT_ID is a project ID that you specified as aconsumer project.

Resolution: Do the following:

1. View all the projects in the organizationto verify that the specified consumer project exists in this organization.
2. View the projectto 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'sowner project (the project used to create the shared reservation) as aconsumer project.

Error message:

ProjectPROJECT_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, soyou 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:

• Specify at least one consumer project to share this reservation with.For more information, seeCreate a shared reservation.
• Use asingle-project reservationinstead of a shared reservation.

Maximum consumer projects exceeded

The following error occurs when a shared reservation has more than 100consumer 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 projectsfor the shared reservation.
2. If you still need to reserve capacity for any omitted projects, thencreate another shared reservationthat is shared with those projects.

Maximum shared reservation count exceeded

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

Error message:

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

Resolution: Follow thebest practiceof minimizing the number of separate shared reservations withthe sameVM propertiesin your organization by doing the following:

• Resize existing reservationsto have larger VM counts. If you have multiple identical shared reservationsthat don't exceed themaximum VM count, thenconsider if you can combine them into fewer shared reservations with the samecombined VM count.

• Modify the consumer projects for a shared reservationto include more projects. For example, if you have multiple sharedreservations with the same VM properties and zone but similar owner andconsumer projects, consider if you can combine them into one sharedreservation that can be consumed by all of these projects.

• Delete shared reservationsthat you no longer need.

Reservations from instance templates creation errors

If you fail to create a reservation byspecifying an instance template,then it might be due to one of the errors in this section.

Cross project referencing is not allowed

The following error occurs when you try to create a reservation by specifying aninstance template from another project.

Error message:

Cross project referencing is not allowed for this resource.

Resolution: Do the following:

1. Make sure that the project ID and instance template's name you specifyin your reservation are correct. To check that an instance template exists,get information about the templateorlist the template.

2. An instance template contains project-specific settings, so you can onlyaccess and use an instance template within the same project. Instead, do oneof the following:

   • To create a reservation by specifying an instance template:

     1. Create a new instance templatewithin your project.

     2. Specify the newly created instance template when creating asingle-projectorshared reservation.

        Caution: Create your reservation in the same region and zone as the resources within the instance template. Any regional or zonal resources that are specified in an instance template—such as a machine type or a Persistent Disk—restrict the use of the template to the locations where those resources exist. For example, if your instance template specifies an existing Persistent Disk inus-central1-a zone, then you must create your reservation in the same zone. Otherwise, creating the reservation or the VMs that can consume the reservation fails.

        To check if an existing template specifies any resources that bind the template to a specific region or zone, get information about the instance template and look for references to regional or zonal resources inside of it.

   • To create a reservation without specifying an instance template, createasingle-projectorshared reservationby specifying VM properties directly.

Instance template not found

The following error occurs when you try to create a reservation by specifying aninstance template that doesn't exist.

Error message:

Source resource reference provided invalid.

Resolution: Check if the name of the instance template you specified iscorrect. Then—after youlist instance templatesto check that your template doesn't exist andonly if your project doesn'thave another template that you want to use—you cancreate a new instance template.

Invalid Local SSD disk size

The following error occurs when you try to create a reservation by specifying aninstance template that includes one or more Local SSD disks, but the templatedoesn't specify the Local SSD disks' size.

Error message:

DiskLOCAL_SSD_NAME provided in the instance template has invalid size: 0 GB.

Resolution: You can't update instance templates. Instead, do the following:

1. Create a new instance template and make sure to specify thedisk size of any Local SSD disks that youinclude in the template.

2. Use the newly created instance template to create asingle-projectorshared reservation.

   Caution: Create your reservation in the same region and zone asthe resources within the instance template. Anyregional orzonal resources that are specified in an instance template—such asa machine type or a Persistent Disk—restrict the use of the templateto the locations where those resources exist. For example, if your instancetemplate specifies an existing disk in theus-central1-a zone,then you must create your reservation in the same zone. Otherwise, creatingthe reservation or the VMs that can consume the reservation fails.

   To check if an existing template specifies any resources that bind thetemplate to a specific region or zone,describe the instance template and look for references to regional orzonal resources inside of it.

3. Optional:Delete the older instance template.

Invalid zone for an instance template

The following error occurs when you try to create a reservation by specifyingan instance template, and you specify an invalid location for your instancetemplate.

Error message:

Reservation cannot be created outside the zone/region of source resource.

Resolution: Do one of the following:

• Make sure to create your reservation in the same region and zone as theresources within the instance template. Anyregionalorzonal resourcesthat are specified in an instance template—such as a machine type or aPersistent Disk—restrict the use of the template to the locationswhere those resources exist. For example, if your instance templatespecifies an existing Persistent Disk in theus-central1-a zone, thenyou must create your reservation in the same zone. Otherwise, creating thereservation or the VMs that can consume the reservation fails.

  To check if an existing template specifies any resources that bind thetemplate to a specific region or zone,get information about the templateand look for references to regional or zonal resources inside of it.

• Use an instance template that doesn't restrict to a specific region or zone.Because you can't update instance templates, do the following:

  1. Create a new instance template based on an existing templatewith the updated properties.

  2. Create asingle-projectorshared reservationby specifying the newly created instance template.

     Caution: Create your reservation in the same region and zoneas the resources within the instance template. Anyregional orzonal resources that are specified in an instancetemplate—such as a machine type or aPersistent Disk—restrict the use of the template to thelocations where those resources exist. For example, if your instancetemplate specifies an existing disk in theus-central1-azone, then you must create your reservation in the same zone. Otherwise,creating the reservation or the VMs that can consume the reservationfails.

     To check if an existing template specifies any resources that bindthe template to a specific region or zone,describe the instance template and look for references to regionalor zonal resources inside of it.

  3. Optional:Delete the older instance template.

Override instance template properties

The following error occurs when you try to create a reservation by specifyingan instance template, and you specify both an instance template and VMproperties when creating the reservation.

Error message:

Reservation cannot override properties populated by source resource.

Resolution: Do one of the following:

• To create a reservation by specifying an instance template, make sure toremoveany field that specifies VM properties.

• To create a reservation by specifying an instance template with differentVM properties, do the following:

  1. You can't update an existing instance template. Instead,create a new instance template based on an existing template.

  2. Specify the newly created instance template when creating asingle-projectorshared reservation.

     Caution: Create your reservation in the same region and zoneas the resources within the instance template. Anyregional orzonal resources that are specified in an instancetemplate—such as a machine type or aPersistent Disk—restrict the use of the template to thelocations where those resources exist. For example, if your instancetemplate specifies an existing disk in theus-central1-azone, then you must create your reservation in the same zone. Otherwise,creating the reservation or the VMs that can consume the reservationfails.

     To check if an existing template specifies any resources that bindthe template to a specific region or zone,describe the instance template and look for references to regionalor zonal resources inside of it.

  3. Optional:Delete the older instance template.

• To create a reservation without specifying an instance template, createinstead asingle-projectorshared reservationby specifying VM properties directly.

Reservations with compact placement policies creation errors

If you fail to create a reservation by specifying acompact placement policy,it might be due to one of the errors in this section.

Attempt to create an automatically consumed reservation

The following error occurs when you try to create an automatically consumedreservation and specify a compact placement policy.

Placement policy only supports specific reservations.

Resolution: You can only specify compact placement policies when creatingspecifically targeted reservations.

Attempt to create a shared reservation

The following error occurs when you try to create a shared reservation byspecifying a compact placement policy.

Error message:

Creating shared reservations with placement policy is not supported.

Resolution: You can specify a compact placement policy only forsingle-project reservations.Thus, create a new reservationand a new compact placement policy for eachproject you wanted to initially share your shared reservation with.

Attempt to specify a policy with amax-distance value of1

The following error occurs when you try to specify a compact placement policywith amax-distance value of1 in a single-project reservation.

Error message:

Resource policies with max-distance less than 2 are not supported.

Resolution: You can't specify compact placement policies with amax-distance value of1 when creating a single-project reservation. Instead,do the following:

1. Create a new compact placement policythat doesn't specify amax-distance value of1.

2. Do one of the following:

   • Create a single-project reservation by specifying an instance templateby doing the following:

     1. You can't modify the properties of an existing instance template.Instead,create a new instance templatethat specifies the newly created compact placement policy.

     2. Create a reservation by specifying the newly created instance template.

     3. Optional:Delete the old instance template.

   • Create a single-project reservation by specifying properties directlyand specify the newly created compact placement policy.

Additionally, if you no longer need the old compact placement policy, see how todelete the placement policy.

Attempt to specify a spread placement policy

The following error occurs when you try to specify a spread placement policy ina reservation.

Error message:

Failed to create reservation with policySPREAD_PLACEMENT_POLICY_NAME. Reservations do not supportspread placement policies.

Resolution: When creating a reservation, you can only specify acompact placement policy.Spread placement policies aren't supported.

Invalid type of resource policy

The following error occurs when you try to create a reservation by specifyinganother type of resource policy.

Error message:

Reservation can only be supported by placement policy.

Resolution: When creating a reservation, you can only specify acompact placement policy.Other types of resource policies, such as instance schedules or snapshotsschedules, aren't supported.

Invalid zone for the policy

The following error occurs when you try to specify a compact placement policy ina reservation, and you specify a zone which isn't within the region of thespecified compact placement policy.

Error message:

ZONE does not match placement policy region.

WhereZONE is the zone where you tried to reserve VMs.

Resolution: Try one of the following:

• Make sure that your zone is within the same region of the compact placementpolicy you specify in a reservation or a reservation's instance template.

• You can't update compact placement policies. Instead, do the following:

  1. Create a new compact placement policywith the updated properties.

  2. Select one of the following methods:

     • Create a new reservation by specifying properties directly, andspecify the newly created compact placement policy.

     • Do the following:

       1. You can't update instance templates. Instead, create a newinstance template byspecifying the newly created compact placement policy.

          Important: Placement policies areregional resources. If you specify a placement policy when creating an instance template, then the policy restricts the use of the template to the region where it exists. For example, if you create a compact placement policy inus-central1, you can only use the template to create VMs or reservations within the same region.

       2. Create a new reservation by specifying the newly createdinstance template.

       3. Optional:Delete the older instance template.

  3. Optional:Delete the older compact placement policy.

Maximum VM count exceeded

The following error occurs when you try to reserve more VMs than the supportedlimit for a compact placement policy with a maximum distance value of2.

Error message:

No more thanSUPPORTED_NUMBER_OF_VMS instances of machine type can be created with this policy.

Resolution: To reserve more than themaximum number of supported VMsfor a compact placement policy with a maximum distance value of2, do one ofthe following:

• Create multiple reservations with matching zone, project, and properties.Since you can't share compact placement policies across reservations, youmust specify a separate policy with a maximum distance value of2 for eachreservation.

• Specify a compact placement policy with a maximum distance value of3(recommended) or without a maximum distance value.

Override compact placement policy

The following error occurs when you try to create a reservation by specifying aninstance template that includes a compact placement policy, and you also specifya compact placement policy directly.

Error message:

Setting resource policy in both reservation and instance template is not allowed.

Resolution: When you create a reservation, you can specify a compactplacement policy either directly or by using an instance template.

To create a reservation by specifying an instance template and a differentpolicy from the one specified in the template, do the following:

1. If you haven't already, thencreate a new compact placement policy.

2. Because you can't update instance templates,create a new template that specifies the new compact placement policy.

3. Create a reservation by specifying the new instance template.

4. Optional:Delete the old instance template.

5. Optional:Delete the old compact placement policy.

The policy is already specified in another reservation

The following error occurs when you try to create a reservation by specifyinga compact placement policy, and the compact placement policy is alreadyspecified in another reservation.

Error message:

Placement policy has been used by another reservation.

Resolution: You can useone compact placement policy only per reservation.You can't share compact placement policies across reservations. If you want touse a similar compact placement policy for another reservation, select one ofthe following methods:

• To create a reservation by specifying an instance template that includes acompact placement policy, follow these steps:

  1. Create a new compact placement policy.

  2. Create a new instance template byspecifying the newly created compact placement policy.

     Important: Placement policies areregional resources. If you specify a placement policy when creating an instance template, then the policy restricts the use of the template to the region where the policy exists. For example, if you create a compact placement policy inus-central1, you can only use the template to create VMs or reservations within the same region.

  3. Create a reservation byspecifying the newly created instance template.

  4. Optional:Delete the older instance template.

• To create a reservation by specifying VM properties and a compact placementpolicy directly, follow these steps:

  1. Create a new compact placement policy.

  2. Create a reservation byspecifying the new compact placement policy directly.

Unsupported machine type

The following error occurs when you try to create a reservation by specifyingan invalid machine type for compact placement policies.

Error message:

Placement policy with reservation is not applicable to machine typeMACHINE_TYPE.

WhereMACHINE_TYPE is the machine type you tried tospecify when creating a reservation.

Resolution: When creating a reservation that specifies a compact placementpolicy, make sure to specify asupported machine typefor compact placement policies.