기본적으로 인스턴스를 만들면 새 부팅 영구 디스크가 생성됩니다.
부팅 디스크의 이름은 VM의 이름과 일치합니다. VM의 이름을 my-instance로 지정하면 디스크 이름도 my-instance입니다. 이 이름의 영구 디스크가 이미 있으면 요청이 실패합니다. 이 문제를 해결하려면 선택적으로 스냅샷을 만든 후 기존 영구 디스크를 삭제하면 됩니다.
인스턴스 템플릿이 올바르지 않음
최근에 인스턴스 템플릿을 업데이트한 경우 MIG에서 VM 만들기에 실패하도록 하는 잘못된 속성이 있을 수 있습니다. 속성에 다음과 같은 일반적인 오류가 있는지 확인합니다.
소스 이미지와 같은 존재하지 않는 리소스를 지정했습니다.
리소스 이름 철자가 틀렸습니다.
부팅 디스크가 아닌 기존 영구 디스크를 읽기/쓰기 모드로 연결하려고 했지만 그룹에 VM이 두 개 이상 포함되어 있습니다. VM이 두 개 이상인 그룹의 경우 그룹의 모든 VM 간에 공유하려는 추가 디스크를 읽기 전용 모드로만 연결할 수 있습니다.
리소스 유형 한도 초과
다음 오류는 한 리전 MIG에서 VM 2,000개 이상 또는 영역 MIG에서 VM 1,000개 이상을 만들려고 시도할 때 발생합니다. 인스턴스 그룹의 크기 한도에 도달했습니다.
오류 메시지:
ERROR: (gcloud.compute.<INSTANCE_GROUP_TYPE>.<METHOD>) Could not
fetch resource:
- Exceeded limit 'MAX_INSTANCES_IN_INSTANCE_GROUP' on resource 'PROJECT_ID'.
Limit: NUMBER
다음 오류는 리전 MIG를 삭제하려고 할 때 --zone 플래그를 지정하고 리전을 지정하지 않을 때 또는 잘못된 리전을 지정할 때 발생합니다.
영역 MIG를 삭제하려고 시도할 때 --region 플래그를 지정한 경우에도 비슷한 오류가 발생할 수 있습니다.
오류 메시지:
ERROR: (gcloud.compute.instance-groups.managed.delete) Some requests did not succeed:
‐ The resource 'projects/PROJECT/zones/ZONE/instanceGroupManagers/INSTANCE_GROUP_NAME' was not found
ERROR: (gcloud.compute.instance-groups.managed.delete) Some requests did not succeed:
‐ The resource 'projects/PROJECT/regions/REGION/instanceGroupManagers/INSTANCE_GROUP_NAME' was not found
부하 분산기의 백엔드 서비스에 사용될 때는 인스턴스 그룹을 삭제할 수 없습니다.
인스턴스 그룹을 삭제하려면 먼저 백엔드 서비스에서 인스턴스를 삭제해야 합니다.
오류 메시지:
ERROR: (gcloud.compute.instance-groups.managed.delete) Some requests did not succeed:
‐ The instance_group_manager resource 'projects/PROJECT/zones/ZONE/instanceGroupManagers/INSTANCE_GROUP_NAME is already being used by 'projects/PROJECT/global/backendServices/BACKEND_SERVICE
ERROR: (gcloud.compute.instance-groups.managed.delete) Some requests did not succeed:
‐ The instance_group_manager resource 'projects/PROJECT/regions/REGION/instanceGroupManagers/INSTANCE_GROUP_NAME is already being used by 'projects/PROJECT/global/backendServices/BACKEND_SERVICE
자동 복구 정책을 구성했지만 상태 확인 프로브가 애플리케이션에 도달하도록 허용하는 방화벽 규칙을 구성하지 않았거나 잘못 구성한 경우 VM이 비정상으로 나타나고 MIG가 계속해서 다시 생성을 시도합니다. 상태 확인 방화벽 규칙을 구성하는 방법에 대한 자세한 내용은 상태 확인 설정 예시를 참조하세요.
[[["이해하기 쉬움","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\u003eManaged instance groups (MIGs) may fail to create or recreate VM instances due to issues like a lingering autoscaler after MIG deletion, or a pre-existing boot disk with the same name as the VM.\u003c/p\u003e\n"],["\u003cp\u003eInvalid instance template properties, such as non-existent resources, misspellings, or incorrect disk attachment modes for multi-VM groups, can prevent MIGs from successfully creating VM instances.\u003c/p\u003e\n"],["\u003cp\u003eExceeding the VM limit per MIG (2,000 for regional, 1,000 for zonal) results in creation failure, which can be resolved by using regional MIGs, splitting workloads across multiple MIGs, or requesting a limit increase.\u003c/p\u003e\n"],["\u003cp\u003eDeleting a MIG might fail if the incorrect region or zone is specified, or if the MIG is still being used by a load balancer's backend service, requiring removal from the backend service first.\u003c/p\u003e\n"],["\u003cp\u003eContinuous instance recreation in a MIG often indicates that health check probes cannot reach the instances due to a missing or misconfigured firewall rule, necessitating a review of the health check firewall settings.\u003c/p\u003e\n"]]],[],null,["# Troubleshooting managed instance groups\n\n*** ** * ** ***\n\nThere are several issues that can prevent a\n[managed instance group (MIG)](/compute/docs/instance-groups#managed_instance_groups)\nfrom successfully creating or recreating a VM instance.\n\nIf logs are generated for a deleted MIG\n---------------------------------------\n\nThe problem might be related to the following situations.\n\n### Attached autoscaler still exists\n\nIf you [deleted](/compute/docs/instance-groups/delete-mig#delete_a_mig)\na MIG using the Compute Engine API and you did not issue a separate request\nto delete the attached autoscaler, the Logs Explorer might show logs with\nthe following message. \n\n```\nThe resource 'projects/PROJECT/zones/ZONE/instanceGroupManagers/DELETED_INSTANCE_GROUP_NAME' was not found.\n```\n\n**Resolution**:\n\nTo resolve this issue, delete the attached autoscaler using the Compute Engine API\nmethods:\n\n- For an autoscaler of a zonal MIG, use the [`autoscalers.delete` method](/compute/docs/reference/rest/v1/autoscalers/delete).\n- For an autoscaler of a regional MIG, use the [`regionAutoscalers.delete` method](/compute/docs/reference/rest/v1/regionAutoscalers/delete).\n\nIf your MIG cannot create or recreate instances\n-----------------------------------------------\n\nThe problem might be related to the following situations.\n\n### The boot disk already exists\n\nBy default, a new boot persistent disk is created when you create an instance.\nThe name of the boot disk matches the name of the VM. If you name a VM\n`my-instance`, the disk is also named `my-instance`. If a persistent disk\nalready exists with that name, the request fails. To resolve this issue, you\ncan optionally [take a snapshot](/compute/docs/disks/create-snapshots), and\nthen delete the existing persistent disk.\n\n### The instance template is not valid\n\nIf you updated your instance template recently, there could be an invalid\nproperty that causes the MIG to fail VM creation. Examine the\nproperties for these common errors:\n\n- You specified a resource that doesn't exist, such as a source image.\n- You misspelled a resource name.\n- You tried to attach an existing non-boot persistent disk in read/write mode but your group contains more than one VM. For groups with more than one VM, any additional disks you want to share between all of the VMs in the group can be attached only in read-only mode.\n\n### Limit exceeded for resource type\n\nThe following error occurs when you try to create more than 2,000 VMs in a\nregional MIG or more than 1,000 VMs in a zonal MIG. You have reached the size\nlimit for your instance group.\n\n**Error message**: \n\n```\nERROR: (gcloud.compute.\u003cINSTANCE_GROUP_TYPE\u003e.\u003cMETHOD\u003e) Could not\nfetch resource:\n\n - Exceeded limit 'MAX_INSTANCES_IN_INSTANCE_GROUP' on resource 'PROJECT_ID'.\n Limit: NUMBER\n```\n\n**Resolution**:\n\nTo resolve this issue, try one of the following:\n\n- If you are using a zonal MIG, use a [regional MIG](/compute/docs/instance-groups#types_of_managed_instance_groups) instead.\n- Create multiple MIGs and split your workload across them---for example by adjusting your [load balancing](/compute/docs/instance-groups/adding-an-instance-group-to-a-load-balancer) configuration.\n- If you still need a bigger group, you can [increase the size limit of your MIG](/compute/docs/instance-groups/add-remove-vms-in-mig#increase_the_groups_size_limit) or [contact support](/support-hub) to make a request.\n\nIf you cannot delete your MIG or its instances\n----------------------------------------------\n\nThe problem might be related to the following situation.\n\n### Resource not found in zone or region\n\nThe following error occurs when you try to delete a regional MIG and you\nspecify the `--zone` flag, specify no region, or specify the wrong region.\nA similar error can occur if you try to delete a zonal MIG and you specify\nthe `--region` flag.\n\n**Error message**:\n\n-\n\n ```\n ERROR: (gcloud.compute.instance-groups.managed.delete) Some requests did not succeed:\n ‐ The resource 'projects/PROJECT/zones/ZONE/instanceGroupManagers/INSTANCE_GROUP_NAME' was not found\n ```\n-\n\n ```\n ERROR: (gcloud.compute.instance-groups.managed.delete) Some requests did not succeed:\n ‐ The resource 'projects/PROJECT/regions/REGION/instanceGroupManagers/INSTANCE_GROUP_NAME' was not found\n ```\n\n**Resolution**:\n\nTo resolve this issue, try one of the following:\n\n- Append the appropriate `--region` or `--zone` flag to your command\n- [Set a default region and zone](/compute/docs/gcloud-compute#default-region-zone)\n\n### Resource is used by a backend service\n\nYou cannot remove an instance group when it is used by a load balancer's backend service.\nYou must remove the instance from the backend service before you can delete the\ninstance group.\n\n**Error message**:\n\n-\n\n ```\n ERROR: (gcloud.compute.instance-groups.managed.delete) Some requests did not succeed:\n ‐ The instance_group_manager resource 'projects/PROJECT/zones/ZONE/instanceGroupManagers/INSTANCE_GROUP_NAME is already being used by 'projects/PROJECT/global/backendServices/BACKEND_SERVICE\n ```\n-\n\n ```\n ERROR: (gcloud.compute.instance-groups.managed.delete) Some requests did not succeed:\n ‐ The instance_group_manager resource 'projects/PROJECT/regions/REGION/instanceGroupManagers/INSTANCE_GROUP_NAME is already being used by 'projects/PROJECT/global/backendServices/BACKEND_SERVICE\n ```\n\n**Resolution**:\n\n1. Optional: Drain the backend instance group.\n\n - For [proxy load balancers only](/load-balancing/docs/choosing-load-balancer#lb-summary),\n you can set the [capacity scaler](/load-balancing/docs/backend-service#capacity_scaler)\n to `0.0` before removing the instance group from a backend service. You can\n set the capacity scaler to zero by using the\n [`gcloud compute backend-services edit` command](/sdk/gcloud/reference/compute/backend-services/edit).\n\n - For both proxy and pass-through load balancers, if you\n [enable connection draining](/load-balancing/docs/enabling-connection-draining)\n on the backend service, Google Cloud attempts to allow existing\n connections to persist, complete, and drain whenever an instance group is\n removed from a backend service.\n\n2. Remove the MIG from the regional or global backend service.\n\n - For a zonal MIG, run the following command:\n\n ```\n gcloud compute backend-services remove-backend BACKEND_SERVICE \\\n --instance-group=INSTANCE_GROUP_NAME \\\n --instance-group-zone=ZONE \\\n [--region=REGION | --global]\n ```\n - For a regional MIG, run the following command:\n\n ```\n gcloud compute backend-services remove-backend BACKEND_SERVICE \\\n --instance-group=INSTANCE_GROUP_NAME \\\n --instance-group-region=REGION \\\n [--region=REGION | --global]\n ```\n3. Delete the MIG:\n\n ```\n gcloud compute instance-groups managed delete INSTANCE_GROUP_NAME\n ```\n\nIf your MIG continually tries to recreate instances\n---------------------------------------------------\n\nThe problem might be related to the following situation.\n\n### Health check probes cannot reach the instance\n\nIf you configured an autohealing policy but you did not configure---or\nmisconfigured---the firewall rule that lets the health check probes reach your\napplication, then your VMs\n[appear unhealthy](/compute/docs/instance-groups/autohealing-instances-in-migs#checking_the_status),\nand the MIG continuously tries to recreate them. For information about how to\nconfigure a health check firewall rule, see\n[Example health check set up](/compute/docs/instance-groups/autohealing-instances-in-migs#example_health_check_set_up)."]]
