The following are known issues within Cloud Quotas.
Inconsistent quota values during rollouts
Google Cloud sometimes changes the default quota values for resources and APIs. These changes take place gradually, which means that during the rollout of a new default quota, the quota value that appears in the Google Cloud console might not reflect the new quota value that is available to you.
For example, suppose that Google Cloud changes the default quota for
firewall rules from 200 to 300, and you use the Google Cloud console to
view your quota, you might see the new quota of 300, even though your
actual quota is 200 until the rollout completes.
If a quota rollout is in progress, you may receive an error message that states
The future limit is the new default quota that will be available after a
service rollout completes. If you see this error message, a service rollout is
in progress, and the cited quota value and future value are correct, even if
what appears in the Google Cloud console is different.
For troubleshooting steps, see Exceeding quota values during a service rollout.
Quota preference contactEmail field is required
To update the QuotaPreference value through the Cloud Quotas API,
the contactEmail field is required. This email address cannot be a group
email.
For examples of using QuotaPreference in the API, see
Implement common use cases.
Requests for adjustments on quotas that have no usage
If you request an adjustment for a quota that has no previous usage, you won't see that quota available in the Google Cloud console. In these cases, you can still request a quota adjustment through the API.
For example, you might clone a project and know ahead of time that you need to
increase the value for
compute.googleapis.com/local_ssd_total_storage_per_vm_family. While you
won't see that quota available in the Google Cloud console, you can still
use the API to request a quota increase.
For more information, see Implement common use cases.