If you perform resource changes such as adding or deleting disks or Compute Engine instances without using Terraform, differences might occur between Terraform templates and created resources.
If you execute Terraform when such differences exist, operations might be unsuccessful.
In such a case, take appropriate action according to the following flowchart.
Storage node differences that can be allowed
The following table shows resource types and contents for which differences are allowed in storage node difference confirmation.
|
Item |
Resource type |
Resource operation |
Resource name |
Points to confirm |
Remarks |
|---|---|---|---|---|---|
|
1 |
google_compute_disk.user_disks[ ] |
create |
<clusterName>-snXX-userdatadiskYY |
Resources for "the number of storage nodes to be created × the number of drives per node" are created. |
If you deleted disks, user disks are also created. |
|
2 |
google_compute_attached_disk.attached_user_disk[ ] |
create |
<clusterName>-snXX |
Resources for "the number of storage nodes to be created × the number of drives per node" are created. |
|
|
3 |
google_compute_instance_group.sdsc-instance-group[0] will be updated in-place |
updated in-place |
- |
This may be updated when resources are created, but ignore the change. |