-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error when destroying and recreating google_compute_per_instance_config/google_compute_region_per_instance_config #9042
error when destroying and recreating google_compute_per_instance_config/google_compute_region_per_instance_config #9042
Comments
note that this can be worked around by calling |
…resources. It's a bit counterintuitive that creating a per-instance config in an IGM spins up an instance but destroying it leaves the instance behind. Also fixed a bug related to the operation to detach the disk from the instance failing due to the instance having been deleted. Fixes hashicorp/terraform-provider-google#9042 & hashicorp/terraform-provider-google#16621.
…resources It's a bit counterintuitive that creating a per-instance config in an IGM spins up an instance but destroying it leaves the instance behind. Also fixed a bug related to the operation to detach the disk from the instance failing due to the instance having been deleted. Fixes hashicorp/terraform-provider-google#9042 & hashicorp/terraform-provider-google#16621.
…resources It's a bit counterintuitive that creating a per-instance config in an IGM spins up an instance but destroying it leaves the instance behind. Also fixed a bug related to the operation to detach the disk from the instance failing due to the instance having been deleted. Other than the tests for the new per-instance config behavior, I was unable to devise an isolated test to trigger this issue. Fixes hashicorp/terraform-provider-google#9042 & hashicorp/terraform-provider-google#16621.
…resources It's a bit counterintuitive that creating a per-instance config in an IGM spins up an instance but destroying it leaves the instance behind. Also fixed a bug related to the operation to detach the disk from the instance failing due to the instance having been deleted. Other than the tests for the new per-instance config behavior, I was unable to devise an isolated test to trigger this issue. Fixes hashicorp/terraform-provider-google#9042 & hashicorp/terraform-provider-google#16621.
…resources It's a bit counterintuitive that creating a per-instance config in an IGM spins up an instance but destroying it leaves the instance behind. Also fixed a bug related to the operation to detach the disk from the instance failing due to the instance having been deleted. Other than the tests for the new per-instance config behavior, I was unable to devise an isolated test to trigger this issue. Fixes hashicorp/terraform-provider-google#9042 & hashicorp/terraform-provider-google#16621.
…resources (#9588) It's a bit counterintuitive that creating a per-instance config in an IGM spins up an instance but destroying it leaves the instance behind. Also fixed a bug related to the operation to detach the disk from the instance failing due to the instance having been deleted. Other than the tests for the new per-instance config behavior, I was unable to devise an isolated test to trigger this issue. Fixes hashicorp/terraform-provider-google#9042 & hashicorp/terraform-provider-google#16621.
…resources (#9588) It's a bit counterintuitive that creating a per-instance config in an IGM spins up an instance but destroying it leaves the instance behind. Also fixed a bug related to the operation to detach the disk from the instance failing due to the instance having been deleted. Other than the tests for the new per-instance config behavior, I was unable to devise an isolated test to trigger this issue. Fixes hashicorp/terraform-provider-google#9042 & hashicorp/terraform-provider-google#16621. [upstream:4153866aaf018b769837b565a1088095fb25ae61] Signed-off-by: Modular Magician <magic-modules@google.com>
…resources (#9588) (#16729) It's a bit counterintuitive that creating a per-instance config in an IGM spins up an instance but destroying it leaves the instance behind. Also fixed a bug related to the operation to detach the disk from the instance failing due to the instance having been deleted. Other than the tests for the new per-instance config behavior, I was unable to devise an isolated test to trigger this issue. Fixes #9042 & #16621. [upstream:4153866aaf018b769837b565a1088095fb25ae61] Signed-off-by: Modular Magician <magic-modules@google.com>
…resources (#9588) (#6724) It's a bit counterintuitive that creating a per-instance config in an IGM spins up an instance but destroying it leaves the instance behind. Also fixed a bug related to the operation to detach the disk from the instance failing due to the instance having been deleted. Other than the tests for the new per-instance config behavior, I was unable to devise an isolated test to trigger this issue. Fixes hashicorp/terraform-provider-google#9042 & hashicorp/terraform-provider-google#16621. [upstream:4153866aaf018b769837b565a1088095fb25ae61] Signed-off-by: Modular Magician <magic-modules@google.com>
…resources (hashicorp#9588) It's a bit counterintuitive that creating a per-instance config in an IGM spins up an instance but destroying it leaves the instance behind. Also fixed a bug related to the operation to detach the disk from the instance failing due to the instance having been deleted. Other than the tests for the new per-instance config behavior, I was unable to devise an isolated test to trigger this issue. Fixes hashicorp#9042 & hashicorp#16621. [upstream:4153866aaf018b769837b565a1088095fb25ae61] Signed-off-by: Modular Magician <magic-modules@google.com>
…resources (#9588) It's a bit counterintuitive that creating a per-instance config in an IGM spins up an instance but destroying it leaves the instance behind. Also fixed a bug related to the operation to detach the disk from the instance failing due to the instance having been deleted. Other than the tests for the new per-instance config behavior, I was unable to devise an isolated test to trigger this issue. Fixes hashicorp/terraform-provider-google#9042 & hashicorp/terraform-provider-google#16621. [upstream:4153866aaf018b769837b565a1088095fb25ae61] Signed-off-by: Modular Magician <magic-modules@google.com>
…resources (#9588) (#1767) It's a bit counterintuitive that creating a per-instance config in an IGM spins up an instance but destroying it leaves the instance behind. Also fixed a bug related to the operation to detach the disk from the instance failing due to the instance having been deleted. Other than the tests for the new per-instance config behavior, I was unable to devise an isolated test to trigger this issue. Fixes hashicorp/terraform-provider-google#9042 & hashicorp/terraform-provider-google#16621. [upstream:4153866aaf018b769837b565a1088095fb25ae61] Signed-off-by: Modular Magician <magic-modules@google.com>
…resources (GoogleCloudPlatform#9588) It's a bit counterintuitive that creating a per-instance config in an IGM spins up an instance but destroying it leaves the instance behind. Also fixed a bug related to the operation to detach the disk from the instance failing due to the instance having been deleted. Other than the tests for the new per-instance config behavior, I was unable to devise an isolated test to trigger this issue. Fixes hashicorp/terraform-provider-google#9042 & hashicorp/terraform-provider-google#16621.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
…resources (GoogleCloudPlatform#9588) It's a bit counterintuitive that creating a per-instance config in an IGM spins up an instance but destroying it leaves the instance behind. Also fixed a bug related to the operation to detach the disk from the instance failing due to the instance having been deleted. Other than the tests for the new per-instance config behavior, I was unable to devise an isolated test to trigger this issue. Fixes hashicorp/terraform-provider-google#9042 & hashicorp/terraform-provider-google#16621.
When a
google_compute_per_instance_config
is created, both a vm and the instance config linked to it are created.However when
google_compute_per_instance_config
is destroyed, the is vm remains untouchedThis leads to errors when a deleted
google_compute_per_instance_config
is subsequently recreated, since a vm with given name already exists as part of the mig.google_compute_per_instance_config
should (on destruction( either delete the vm instance it initially creates (via instanceGroupManagers/deleteInstances), or provide a flag to toggle this behaviour.I'm happy to submit a PR.
Note: in the example below
google_compute_region_instance_group_manager.target_size
is set tonull
for the reason provided in the comment.Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
terraform --version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Actual Behavior
Steps to Reproduce
after running:
I get the following error:
Important Factoids
References
The text was updated successfully, but these errors were encountered: