This document describes how to resolve issues with consumingreservations of Compute Engine zonal resources.

Fewer VMs available for consumption

Issue: The number of physically reserved VMs (theassuredCount field)doesn't match the number of reserved VMs specified in a reservation (thecountfield). This means that fewer VMs are reserved for your project and any projectswith which a shared reservation is shared.

This issue can occur for one or more of the following reasons:

• A shared reservation's consumer project wassuspended ormigrated to another organization.In this case, Compute Engine decreases theassuredCount field bythe number of VMs that the consumer project is consuming.

• The project in which the reservation was created was suspended. In thiscase, Compute Engine sets theassuredCount field to0.

• A host error impacted the reservation.

Resolution: Unless the project in which the reservation was created wassuspended, Compute Engine makes best effort to automatically resolve adiscrepancy between theassuredCount andcount fields in a reservationwithin 24 hours. Additionally, until this discrepancy is resolved, Google Cloudbills you only for the physically reserved capacity.

Important: If this issue isn't resolved within 48 hours, or the project in whichthe reservation was created was suspended, then contact your assignedTechnical Account Manager (TAM) orsupport.

Issues for VMs not consuming reservations

If a VM can't consume a reservation, then it might be due to one or more of thefollowing issues:

• The reservation and VM's properties don't match

• The VM's reservation affinity is incorrect

• The reservation is already fully consumed

• The quota for the shared reservations is exceeded

This section describes how to identify each of these issues, resolve each ofthem, and verify reservations consumption.

Mismatched VM properties

Issue: A VM can't consume a reservation with differentVM properties.

To identify which properties aren't matching between the VM and reservation,view the properties of the reservation and the VM by doing the following:

1. View the details of the reservation

2. View the details of the VM

Then, compare the two outputs to verify that the following propertiesexactlymatch:

• project

  • If the reservation is shared with multiple projects (specifically, ifthe reservation has theshareType field set toSPECIFIC_PROJECTS),then the VMs can be located in the project where the reservation wascreated (the owner project), or in any projects that the reservation isshared with (consumer projects).

• zone

• machineType

• guestAccelerators.acceleratorType (if any)

• guestAccelerators.acceleratorCount (if any)

• minCpuPlatform

  • The VM and reservation must have the exact sameminCpuPlatformconfiguration. For example, settingminCpuPlatform toIntel Broadwell when creating a VM won't match theminCpuPlatformvalue ofAutomatic within a reservation.

• localSsds.interface (if any)

  • The reservation and VM must have the same number of local SSD disks witha matchinglocalSsds.interface property for each local SSD disk.

• resourcePolicies (if any)

  • Only if a reservation specifies acompact placement policy.

• locationHint (if any)

  • Only if a reservation specifies thelocationHint field. You canspecify thelocationHint field only when creating VMs usingREST.

Resolution: After identifying the properties that don't match, try one ofthe following:

• If the VM properties don't match the reservation, then do one of thefollowing:

  • Delete the VM and create anew VM with properties that match the reservation's properties.

  • Update the VM tomatch the reservation's properties.

• If the reservation's properties are supposed to match the VM's properties,thendelete the reservationandcreate a new reservationthat matches the VM's properties. Optionally, you can create aspecific reservation.When creating VMs to consume a specific reservation, you encounter errors ifthe VM's properties don't match the reservation's properties.

After updating the VM or creating a new reservation, check if the VM isconsuming the reservation byverifying the reservation consumption.

Reservation affinity is incorrect

Issue: Thereservation affinityof the VM is misconfigured. The reservation affinity of a VM controls thereservations that a VM can consume. To check your VM's reservation affinity, dothe following:

1. View the details of a reservationand verify if the reservation is an automatically consumed or specificreservation. For more information, seeConsumption type.

2. View the details of the VM andverify the reservation affinity.

Resolution: If the reservation affinity of the VM and the reservation don'tmatch, then do one of the following:

• Create a new VM with a reservation affinity property that matches thereservation's type.

• Update thereservationAffinity property in the VMto specify whether the VM can consume any matching reservation or a specificreservation. To finalize the VM's update, you must restart the VM.

To check if the VM is consuming the reservation, seeVerify reservation consumption.

Reservation is already fully consumed

Issue: The number of VMs consuming this reservation matches thereservation's total number of reserved VMs. This indicates that the reservationis fully consumed.

Resolution: To verify if the reservation is fully consumed,view the details of the reservation,and then verify that the number of VMs consuming the reservation matches thetotal number of reserved VMs in the reservation.

If the reservation is fully consumed, then try one of the following:

• Increase the number of reserved VMs bymodifying the number of reserved VMs in a reservation.

• If the reservation already reserves themaximum number of VMs,then create a new reservation.

• Reduce the number of VMs that are consuming the reservation. For moreinformation, seeVMs unintentionally consuming reservations.

If the reservation is not fully consumed but the VM is not consuming thereservation, then you can further troubleshoot the issue by doing the following:

1. Create a specific reservation with matching properties.

2. Create a VM to consume the reservation. If the VM and the reservationproperties don't match, then creating the VM fails.

Resource quota exceeded for shared reservations

Issue: A VM isn't consuming a shared reservation because your projectdoesn't have sufficient quota for the resources that you're trying to consume.

Resolution: Shared reservations haveadditional quota requirements.If you need to increase quota in your project to consume the reserved resources,then seeRequest a quota adjustment inthe Cloud Quotas documentation.

VM count not restored after stopping or deleting a VM

Issue: If you stop, suspend, or delete a VM that is consuming a reservation,then the operation must complete before the VM no longer counts against thereservation, and the previously consumed resources are again available forconsumption.

Resolution: Wait for a few minutes for the stop, suspend, or deleteoperation on the VMs to complete. Then, to verify that the stopped, suspended,or deleted VMs no longer count against the reservation, check the total numberof consumed VMs in the reservation by using one of the following methods:

• Recommended:Monitor the reservation andlook for a change in the measurements of the reservation.

• View the details of the reservationand check if the value of theinUseCount field decreased. If its valuedidn't decrease, then one or more VMs have started consuming the reservationwhile the stop, suspend, or delete operation was completing.

VM unintentionally consuming reservations

Issue: When you createreservations that are automatically consumed(default), a VM might unintentionally consume these reservations.

Resolution: To avoid that one or more VMs unintentionally consume areservation, do one of the following:

• Create VMs that can't consume any reservations

• Create reservations that can be consumed only when specifically targeted