Reference For: administrators, tenants

Quota errors

Causes and remedies for the error code raised when an operation exceeds the quota of a tenant.

error.quota.exceeded

Text in the console
The tenant's quota for {resource} is {limit}; {current} are in use and {requested} more were asked for.
Meaning for API clients
The operation would take the tenant over its quota of resource (vcpus, memoryMib, diskGib, vms, publicIpv4, snapshots).
Code
FAILED_PRECONDITION, HTTP 412
ArgumentWhat it holds
resourcethe quota that is exceeded.
limitthe quota of the tenant for that resource.
currentthe amount in use.
requestedthe amount that the operation asks for.
tenantthe id of the tenant.

Cause. The operation would take the tenant over its quota of one resource. The resources are vcpus, memoryMib, diskGib, vms, publicIpv4 and snapshots. The message shows the quota, the amount in use and the amount that the operation asks for.

Remedy.

  1. Free the resource: delete servers, snapshots or disks that are no longer needed, or return public addresses.
  2. Choose a smaller plan, or fewer servers.
  3. An administrator can raise the quota. Read the current quota first: kyvernon tenants get <tenant>. Then replace it with the new values: kyvernon tenants quota <tenant> --body-file <file>. The body replaces the whole quota. In the console, use Quota.
  4. When you cannot change the quota yourself, pass on the message id, the name of the resource and the amount that you need.

See the page Self-service concepts.

Version 0.1. Last changed: 2026-11-13