generic::invalid_argument: Accelerator type v2-512 as preemptible (false) and
reserved (false) is not available in zone us-central1-a, please contact support.
generic::permission_denied: Cloud TPU got permissions denied when trying to
access the customer project. Make sure that the IAM account
'service-[project number]@cloud-tpu.iam.gserviceaccount.com' has the 'Cloud
TPU API Service Agent' role by following https://cloud.google.com/iam/docs/manage-access-service-accounts
解决方案
如果用户尝试在未经 IAM 授权的情况下在项目中创建或列出节点，则会发生此错误。此问题可能的原因是 Cloud TPU API 服务账号没有该项目所需的角色。管理访问账号文档简要介绍了如何管理访问权限。按照授予或撤消单个角色中的步骤操作，并为账号“service-PROJECT_NUMBER@cloud-tpu.iam.gserviceaccount.com”授予“Cloud TPU API Service Agent”角色（请务必将 PROJECT_NUMBER 替换为您的项目编号，可在 Google Cloud 控制台的项目设置中找到）。如需详细了解服务代理，请参阅服务代理文档。
超出配额
错误消息
You have reached XXXX limit. Please request an increase for the 'YYYY' quota for
Compute Engine API by following https://cloud.google.com/docs/quotas/view-manage#requesting_higher_quota.
解决方案
您的项目已达到配额限制。如需详细了解如何使用配额，请参阅 Cloud 配额文档。请勿将此配额与 TPU 配额混淆，后者用于控制 TPU Pod 的使用情况。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[],[],null,["# Cloud TPU Error Glossary\n========================\n\nThis document provides a glossary of common errors with solutions from the Cloud TPU service.\n\n*** ** * ** ***\n\nInvalid Accelerator Type\n------------------------\n\n### **Error Message**\n\n```\ngeneric::invalid_argument: Accelerator type v2-512 as preemptible (false) and\nreserved (false) is not available in zone us-central1-a, please contact support.\n```\n\n### **Solution**\n\nAn invalid parameter has been provided to the create command. The availability\nof an accelerator in a zone depends on the following parameters: the type, the\n`preemptible` flag, the `spot` flag, and the `reserved` flag. The `preemptible`, `spot`,\nand `reserved` flags can be changed by including or excluding them in the create\ncommand.\n\nA TPU created with the `reserved` flag will use reserved\ncapacity. Including the `spot` or `preemptible` flags will allow the TPU to be preempted by\nhigher priority TPUs. If none of these flags are provided, the TPU will be on-demand. It is\nnot a valid configuration to enable more than one of these flags. See the\n[create command documentation](/sdk/gcloud/reference/compute/tpus/create) for more information.\n\nThe accelerator types available in each zone can be found in the [TPU regions and zones documentation](/tpu/docs/regions-zones) or they can be\nqueried using the [accelerator-types list command](/sdk/gcloud/reference/compute/tpus/accelerator-types/list). Change the create command to use one\nof these accelerator types and try again or contact support if the problem persists.\n\nNetwork Not Found\n-----------------\n\n### **Error Message**\n\n```\n Cloud TPU received a bad request. The field \"Network\" cannot be \"xxxx\":\n requested resource not found\n```\n\n### **Solution**\n\nThe Network xxxx was not found. Ensure that the Network was created\nand set up properly. See [Create and manage VPC networks](/vpc/docs/create-modify-vpc-networks) for more information.\n\nService Account Permission Denied\n---------------------------------\n\n### **Error Message**\n\n```\n generic::permission_denied: Cloud TPU got permissions denied when trying to\n access the customer project. Make sure that the IAM account\n 'service-[project number]@cloud-tpu.iam.gserviceaccount.com' has the 'Cloud\n TPU API Service Agent' role by following https://cloud.google.com/iam/docs/manage-access-service-accounts\n```\n\n### **Solution**\n\nThis error occurs when a user attempts to create or list nodes in a project\nwithout IAM authorization. A likely cause of this issue is that the Cloud TPU API service\naccount does not have the required role for the project. The [Manage access accounts documentation](/iam/docs/manage-access-service-accounts)\ngives an overview of how to manage access. Follow the [Grant or revoke a single role](/iam/docs/manage-access-service-accounts#single-role) steps\nand give the account 'service-\u003cvar translate=\"no\"\u003ePROJECT_NUMBER\u003c/var\u003e@cloud-tpu.iam.gserviceaccount.com' the role of 'Cloud TPU API Service Agent' (be sure to replace \u003cvar translate=\"no\"\u003ePROJECT_NUMBER\u003c/var\u003e\nwith your project number, which can be found in the project settings in the Google Cloud console). For more\ninformation on service agents, see the [Service agents documentation](/iam/docs/service-agents).\n\nQuota Exceeded\n--------------\n\n### **Error Message**\n\n```\nYou have reached XXXX limit. Please request an increase for the 'YYYY' quota for\nCompute Engine API by following https://cloud.google.com/docs/quotas/view-manage#requesting_higher_quota.\n```\n\n### **Solution**\n\nYour project has reached a quota limit. To learn more about working with quotas, see the [Cloud Quotas documentation](/docs/quotas/overview). This shouldn't be confused with the [TPU quota](/tpu/docs/quota), which governs the usage of TPU pods.\n\nYou may request an increase to the appropriate limit by following the steps listed at [Request a quota adjustment](/docs/quotas/view-manage#requesting_higher_quota). On the quotas page, you may search for the quota specified by the 'YYYY' part of this message. Some quotas are split across different regions or services. The error message will indicate which one needs to be increased.\n\nThe 'XXXX' and 'YYYY' parts of the message may be one of the following:\n\n- HEALTH_CHECKS - 'Health checks' quota\n- FIREWALLS - 'Firewall rules' quota\n- NETWORK_ENDPOINT_GROUPS - 'Network endpoint groups' quota for this region\n- READ_REQUESTS - 'Read requests per minute' quota for the Compute Engine API service\n- OPERATION_READ_REQUESTS - 'Operation read requests per minute' quota\n\nThis request is typically processed within 2-3 business days. If the request is urgent, reach out to a customer engineer or technical account manager."]]
