A managed instance group has triggered an alert indicating that it failed to create new instances. You need to ensure the number of running instances stays at the level specified by the template so the application can handle expected traffic. What should you do?
A Create an instance template that contains valid syntax which will be used by the instance group. Delete any persistent disks with the same name as instance names. B Create an instance template that contains valid syntax that will be used by the instance group. Verify that the instance name and persistent disk name values are not the same in the template. C Verify that the instance template being used by the instance group contains valid syntax. Delete any persistent disks with the same name as instance names. Set the disks.autoDelete property to true in the instance template. D Delete the current instance template and replace it with a new instance template. Verify that the instance name and persistent disk name values are not the same in the template. Set the disks.autoDelete property to true in the instance template. Show Answer Answer Explanation When a managed instance group cannot create new VM instances, a frequent cause is that the boot persistent disk—by default named identically to the instance—already exists because a prior instance's disk was never auto-deleted (disks.autoDelete was false). Google Cloud's troubleshooting guidance for this scenario is to confirm the instance template has valid syntax, remove (optionally after snapshotting) any persistent disks that share a name with the instances the group needs to create, and set disks.autoDelete to true in the template so leftover disks no longer block future instance creation after deletions or autohealing events.
Learn more
Community Discussion