Your managed instance group raised an alert stating that new instance creation has failed to create new instances. You need to solve the instance creation problem. 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.
C is eliminated because you cannot update or modify an existing instance template. It is immutable.
https://cloud.google.com/compute/docs/instance-templates#how_to_update_instance_templates
D is eliminated because you cannot delete an instance template if a managed instance group references it.
https://cloud.google.com/compute/docs/instance-templates/get-list-delete-instance-templates#delete_an_instance_template
B is eliminated because you cannot set different/custom name for persistent disk in an instance template.
https://cloud.google.com/sdk/gcloud/reference/compute/instance-templates/create#--create-disk
So we left with A. Therefore A is the correct answer. Although, it should set the disks.autoDelete property to true for completeness.
When a managed instance group raises an alert indicating that new instance creation has failed, it's important to investigate the issue. This issue is typically related to the configuration of the instance template used by the group. Therefore, the first step is to verify that the instance template being utilized by the instance group contains valid syntax. This includes checking all settings such as machine type, boot disk, and any custom configurations. Valid syntax ensures that the instances created adhere to the specified configurations.
Existing instance group has already template so no requirement to create new one. Problem is with persistent disk so delete it and configure autodelete solves problem now and in future
https://cloud.google.com/compute/docs/instance-templates#how_to_update_instance_templates
Instance templates are designed to create instances with identical configurations. So you cannot update an existing instance template or change an instance template after you create it.
If you need to make changes to the configuration, create a new instance template.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
scanner2
Highly Voted 1 year, 3 months agoEnamfrancis
Most Recent 2 months agoDewansh
12 months agorecluse7
1 year agoEll89
1 year, 1 month ago[Removed]
1 year, 3 months ago3arle
1 year, 3 months ago3arle
1 year, 3 months ago[Removed]
1 year, 3 months agohappydays
1 year, 3 months ago