This document explains how to resolve issues when creating or modifying future reservation requests for Compute Engine zonal resources.
General future reservation requests errors
This section describes the errors that might prevent you from creating or modifying a future reservation request.
Can't access and see future reservations
If you can't access and use future reservations in the gcloud CLI or Compute Engine API, then you might not be eligible to access and use future reservations at this time. In that case, contact your Technical Account Manager or the Sales Team.
Exceeded maximum number of consumer projects
The following error occurs when you specify more than 100 consumer projects for a shared future reservation request.
Error message:
Can only share with at most 100 projects.
Resolution: You can specify up to 100 consumer projects for a shared future reservation request. If you want to specify more, then create multiple shared future reservation requests. For more information, see the best practices for shared on-demand reservations.
Invalid deletion time for the auto-created reservations
The following error occurs when you specify an invalid deletion time for the auto-created reservations for a future reservation request.
Error message:
Auto-created reservations cannot be deleted before future reservation end time.
Resolution: You can only delete an auto-created reservation for a future
reservation after the end time of the reservation period. To view the date and
time when you can delete an auto-created reservation,
view the details of the reservation
and look for the value of the deleteAtTime field.
Invalid end time
The following error occurs when you specify an invalid duration for the reservation period of a future reservation request.
Error message:
Future reservation end time must be at least 24 hours later than start time.
Resolution: The end time of a reservation period must be at least 24 hours later than the start time of the reservation period. Additionally, to increase the likelihood that Google Cloud approves your future reservation request, make sure to specify one of the recommended values for your reservation period.
Invalid start time
The following error occurs when you specify an invalid start time for the reservation period of a future reservation request.
Error messages:
Future reservation start time is either in the past or too early.
Resolution: When creating or modifying a future reservation request, make sure to specify a start time of the reservation period that is at least 1 hour later than the date and time at which you submit a future reservation request for review. However, to increase the likelihood that Google Cloud approves your future reservation request, specifying a recommended value for the start time is recommended.
Overlapping consumer projects
The following error occurs when your current project, or a project you want to share a future reservation request with, contains one or both of the following:
A shared reservation with matching VM properties and zone that specifies a consumer project that isn't specified in the future reservation request that you want to create.
A future reservation request with matching VM properties and zone that specifies an owner or consumer project that is not specified in the future reservation request that you want to create.
Error message:
Future reservation with conflicting projects and matching instance properties with existing and overlapping shared projects is not allowed.
Resolution: When you're creating a future reservation request, make sure to follow the restrictions for creating future reservation requests.
If you need to delete or modify auto-created reservations, on-demand reservations, or future reservation requests to stop them from restricting the type of future reservation requests that you can create, then do one or more of the following:
Modify existing draft or approved shared future reservation requests to change their consumer projects or share type.
Modify existing on-demand or auto-created reservations to modify their consumer projects. You can only modify an auto-created reservation after the end of its reservation period.
Delete any existing future reservation requests before the start time of its reservation period or after the end time of its reservation period.
Delete any existing on-demand or auto-created reservations. You can only delete an auto-created reservation after the end of its reservation period.
Overlapping reservation periods
The following error occurs when the reservation period of your future reservation request overlaps with the reservation period of an existing future reservation request with matching VM properties and zone.
The existing future reservation request can be either located in the same project of your reservation request or in a project you want to share your future reservation request with.
Error message:
Future reservation with overlapping time window for same instance properties and overlapping shared projects is not allowed.
Resolution: Try one of the following:
Modify the reservation period of the future reservation request that you're creating.
Modify the reservation period of an existing draft or approved future reservation request
Delete an existing future reservation request and stop it from restricting the reservation period of the future reservation request that you're creating.
Project without an organization
The following error occurs when you specify a project that doesn't belong to an organization.
Error message:
Cannot create Shared Future Reservations in a project that does not belong to an organization.
Resolution: Try one of the following:
Migrate your current project to an organization and then create the shared future reservation request.
Create a shared future reservation request in a project that belongs to the organization where you want to create the future reservation request.
Future reservation requests errors from instance templates
This section describes the errors that might prevent you from creating a future reservation request by specifying an instance template.
Cross project referencing is not allowed
The following error occurs when you try to create a future reservation request by specifying an instance template from another project.
Error message:
Cross project referencing is not allowed for this resource.
Resolution: Do the following:
Make sure that the project ID and instance template's name you specify in your future reservation request are correct. To check that an instance template exists, get information about the template.
An instance template contains project-specific settings, so you can only access and use an instance template within the same project. Instead, do one of the following:
To create a future reservation request by specifying an instance template:
Create a new instance template within your project.
Specify the newly created instance template when creating a single-project or shared future reservation request.
To create a future reservation request without specifying an instance template, create instead a single-project or shared reservation request by specifying VM properties directly.
Invalid Local SSD disk size
The following error occurs when you try to create a future reservation request by specifying an instance template that includes a Local SSD disk, but the template doesn't specify the Local SSD disk's size.
Error message:
Disk LOCAL_SSD_NAME provided in the instance template has invalid size: 0 GB.
Resolution: You can't update instance templates. Instead, do the following:
Create a new instance template and make sure to specify the disk size of any Local SSD disks that you include in the template.
Use the newly created instance template to create a single-project or shared future reservation request.
Optional: Delete the older instance template.
Invalid zone for an instance template
The following error occurs when you try to create a future reservation request by specifying an instance template with an invalid location for your template.
Error message:
Future reservation cannot be created outside the zone/region of source resource.
Resolution: Do one of the following:
Make sure to create your future reservation request 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 in the
us-central1-azone, then you must create your future reservation request in the same zone. Otherwise, creating the future reservation request fails.To check if an existing template specifies any resources that bind the template to a specific region or zone, get information about the template and 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:
Create a new instance template based on an existing template with the updated properties.
Create a single-project or shared future reservation request. by specifying the newly created instance template.
Optional: Delete the older instance template.
Override instance template properties
The following error occurs when you try to create a future reservation request by specifying both an instance template and VM properties.
Error message:
InstanceProperties cannot be specified while an instance template is being provided.
Resolution: Do one of the following:
To create a future reservation request by specifying an instance template, make sure to remove any field that specifies VM properties.
To create a future reservation request by specifying an instance template with different VM properties, do the following:
You can't update an existing instance template. Instead, create a new instance template based on an existing template.
Specify the newly created instance template when creating a single-project or shared future reservation request.
Optional: Delete the older instance template.
To create a future reservation request without specifying an instance template, create instead a single-project or shared future reservation request by specifying VM properties directly.