-
Notifications
You must be signed in to change notification settings - Fork 140
[Bug] Failed to run terraform destroy in the first time when you have vms with sshkey #194
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
Labels
Comments
Merged
This issue has been fixed in V1.23.0, please upgrade and have a try. |
@oliverpei , thanks for update , but I still get issue, here is a part of log:
|
Merged
@LipingMao Sorry for the trouble, we have fixed in V1.24.0, please have a try. |
OK for me to close this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I get issue when I run terraform destroy, in the case I have two vms with sshkey.
Terraform Version
# terraform -v Terraform v0.12.13 + provider.tencentcloud v1.22.0
Affected Resource(s)
Terraform Configuration Files
create two CVM with sshkey, then run terraform destroy
Expected Behavior
Destroy success.
Actual Behavior
CVM can be destroy, but sshkey destroy failed with the following error:
Error: [TencentCloudSDKError] Code=InvalidInstanceId.NotFound, Message=The specified instance ID `['ins-imyqycsv', 'ins-2o89fojz']` is not found., RequestId=457cd512-2d34-45e9-99df-376c67f9ad8b
if you run terraform destroy again, it can success.
Steps to Reproduce
Write a tf which create 2 CVM with sshkey, then terraform apply, terraform destroy can 100% reproduce this issue.
There is work around which can avoid this issue with limit parallelism to 1 when destroy.
The issue seems like when the code in destroy key pair try to unbind with CVM, but the VM has been deleted. Seems like something wrong here:
https://github.com/terraform-providers/terraform-provider-tencentcloud/blob/master/tencentcloud/resource_tc_key_pair.go#L185-L196
The text was updated successfully, but these errors were encountered: