VM을 만들 때 다음 API 응답 필드가 있으면 초당 요청 20개에 도달했거나 초당 10개가 넘는 일괄 작업이 동시에 실행된 것입니다.
API 응답 필드:
HTTP 403
"reason": "rateLimitExceeded"
이 문제를 해결하려면 일부 요청이 완료될 때까지 기다린 후에 다시 요청해 보세요.
용량 부족
VM을 만들 때 다음 API 응답 필드가 있으면 VM을 만들려고 하는 리전 또는 영역의 용량이 부족한 것입니다.
API 응답 필드:
HTTP 503
"reason": "insufficientCapacity"
이 문제를 해결하려면 다음 중 한 가지를 따르세요.
다른 리전에 VM 만들기
영역 엔드포인트를 사용하는 경우 다른 영역에 VM 만들기
다른 VM 구성 시도
나중에 요청 재시도
요청 상태 오류
일괄 인스턴스 API를 사용하여 VM을 만들 때 요청이 성공적으로 시작되면 create 요청에서 HTTP 200 OK를 RUNNING 상태로 반환합니다.
하지만 요청이 완료되기 전에 실패할 수 있습니다. 요청 상태를 확인하여 요청이 성공적으로 완료되었는지 확인할 수 있습니다. 요청이 성공적으로 완료되지 않으면 다음 요청 상태 중 하나가 표시됩니다.
할당량 초과
작업을 폴링할 때 다음 API 응답 필드가 있으면 리소스의 할당량 한도에 도달하여 요청이 실패한 것입니다. 할당량에 대한 자세한 내용은 리소스 할당량을 참조하세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-03(UTC)"],[[["\u003cp\u003eThis document guides you through troubleshooting common errors encountered when using the bulk instance API for creating virtual machines (VMs).\u003c/p\u003e\n"],["\u003cp\u003eErrors during the initial API request can be caused by invalid syntax, exceeding resource quotas, reaching rate limits, or insufficient capacity, each with specific \u003ccode\u003eHTTP\u003c/code\u003e and \u003ccode\u003e"reason"\u003c/code\u003e codes.\u003c/p\u003e\n"],["\u003cp\u003eRequest status errors, identified through polling, can indicate that a request failed due to quota limits, a resource already existing, or insufficient capacity.\u003c/p\u003e\n"],["\u003cp\u003eEach error type has specific resolutions, such as modifying the request, reducing the number of VMs, requesting a quota increase, or trying a different region, zone or VM config.\u003c/p\u003e\n"],["\u003cp\u003eThe document helps understand how to read the API response and understand error messages, allowing you to correct the request parameters and properly retry.\u003c/p\u003e\n"]]],[],null,["# Troubleshooting bulk VM creation\n\n*** ** * ** ***\n\nThis document shows you how to resolve issues with\n[bulk instance API](/compute/docs/instances/using-bulk-api) creation operations.\n\nOperation errors\n----------------\n\nWhen you use the bulk instance API to create VMs, `create` requests return\n`HTTP 200 OK` with a status of `RUNNING` if the request starts successfully. If\nthe request doesn't start successfully, the API returns one of the responses\nbelow.\n\n### Invalid\n\nIf the following API response fields are present when you create VMs, your API\nrequest isn't written correctly, or it uses a property that isn't supported\nby the bulk API.\n\n**API response fields:**\n\n- `HTTP 400`\n- `\"reason\": \"invalid\"`\n\nTo resolve this issue, do the following:\n\n1. View the `message` field in the response to determine which property in the request caused the error.\n2. Update the property that caused the error.\n3. Retry the request.\n4. If the request fails again, try using the API Explorer to validate the request. For more information, see [Validating API requests](/compute/docs/api/how-tos/api-requests-responses#validating_api_requests).\n\n### Quota exceeded\n\nIf the following API response fields are present when you create VMs, you\nreached a quota limit for a resource. For more information about quotas, see\n[Resource quotas](/compute/quotas).\n\n**API response fields:**\n\n- `HTTP 403`\n- `\"reason\": \"quotaExceeded\"`\n\nTo resolve this issue, do the following:\n\n\u003cbr /\u003e\n\n1. View the \\`message\\` field to identify which resource quota the request exceeded.\n2. Do one of the following:\n - Retry the request with a smaller number of VMs\n - [Request an increase in quota](/compute/quotas#requesting_additional_quota)\n\n\u003cbr /\u003e\n\n### Rate limit exceeded\n\nIf the following API response fields are present when you create VMs, you\nreached the 20 request per second request limit or you have more than 10 bulk\noperations running at the same time.\n\n**API response fields:**\n\n- `HTTP 403`\n- `\"reason\": \"rateLimitExceeded\"`\n\nTo resolve this issue, wait until some requests complete and try your request\nagain.\n\n### Insufficient capacity\n\nIf the following API response fields are present when you create VMs, the region\nor zone you tried to create VMs in has\ninsufficient capacity.\n\n**API response fields:**\n\n- `HTTP 503`\n- `\"reason\": \"insufficientCapacity\"`\n\nTo resolve this issue, do one of the following:\n\n\u003cbr /\u003e\n\n- Create VMs in a different region\n- Create VMs in a different zone if using the zonal endpoint\n- Try a different VM configuration\n- Retry your request later\n\n\u003cbr /\u003e\n\nRequest status errors\n---------------------\n\nWhen you use the bulk instance API to create VMs, your `create` request returns\n`HTTP 200 OK` with a status of `RUNNING` if the request starts successfully.\nHowever, the request may fail before it completes. You can\n[check the status of your request](/compute/docs/instances/using-bulk-api#checking_the_status_of_vms_created_with_the_bulk_instance_api)\nto ensure the request completed successfully. If the request didn't complete\nsuccessfully, you see one of the following request statuses.\n\n### Quota exceeded\n\nIf the following API response fields are present when you poll operations, your\nrequest failed because you reached a quota limit for a resource. For more\ninformation about quotas, see [Resource quotas](/compute/quotas).\n\n**API response fields:**\n\n- `\"status\": \"done\"`\n- `\"httpErrorMessage\": \"FORBIDDEN\"`\n- `\"code\"\": \"QUOTA_EXCEEDED\"`\n\n\nTo resolve this issue, do the following:\n\n1. View the \\`message\\` field to identify which resource quota the request exceeded.\n2. Do one of the following:\n - Retry the request with a smaller number of VMs\n - [Request an increase in quota](/compute/quotas#requesting_additional_quota)\n\n\u003cbr /\u003e\n\n### Resource already exists\n\nIf the following API response fields are present when you poll operations, your\nrequest failed because it tried to create a resource that already exists.\n\n**API response fields:**\n\n- `code: RESOURCE_ALREADY_EXISTS`\n- `httpErrorMessage: CONFLICT`\n- `status: DONE`\n\nTo resolve this issue, do the following:\n\n1. View the `message` field to identify the name of the resource that already exists.\n2. Retry your request using a different `namePattern`. For more information, see [Creating multiple VMs in a region](/compute/docs/instances/using-bulk-api#creating_multiple_vms_in_a_region).\n\n### Insufficient capacity\n\nIf the following API response fields are present when you poll operations, your\nrequest failed because the region or zone (if using the zonal endpoint) you\ntried to create VMs in has insufficient capacity.\n\n**API response fields:**\n\n- `\"status\": \"DONE\"`\n- `\"httpErrorMessage\": \"SERVICE UNAVAILABLE\"`\n- `\"code\": \"ZONE_RESOURCE_POOL_EXHAUSTED\"`\n\n\nTo resolve this issue, do one of the following:\n\n- Create VMs in a different region\n- Create VMs in a different zone if using the zonal endpoint\n- Try a different VM configuration\n- Retry your request later\n\n\u003cbr /\u003e\n\nWhat's next?\n------------\n\n- To learn more about using the bulk instance API, review [Using the bulk instance API](https://cloud.google.com/compute/docs/instances/using-bulk-api)."]]
