-
Notifications
You must be signed in to change notification settings - Fork 674
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
subnet destroy fails immediately after cluster destroy unless delay added #2779
Comments
Can we get error log of subnet destroy? |
@kavya498 Here you go:
|
@deepaksibm FYI |
@kavya498 Has anyone looked into this? I think this happens if you create an OpenShift VPC Gen2 cluster, and then destroy it, and the subnets straight away. The problem is the VPC load balancer that is auto created by the ingress running on the cluster is actually still creating, so by the time the subnet destroy is attempted, even though the cluster is blown away, the VPC load balancer is still in a creation state, and so the subnet cannot be blown away. |
Hi @ocofaigh , we are working on this issue. will roll out a possible fix soon. Will keep posted. |
@deepaksibm I see #2895 was merged, can you confirm what version of the ibm provider it is in? |
Also note that in the merged PR the err returned from the new retry func (if it didn’t succeed and returned one) is not getting checked https://github.com/IBM-Cloud/terraform-provider-ibm/pull/2895/files#diff-8aa3d2a6377c1a49177482cb1ef79891182de2ee27fc46b2e75baf097868bc28R623 and will instead be ignored and overwritten by the subsequent |
Available in 1.30.0.. |
When destroying a VPC Gen2 Openshift cluster the provider does not wait long enough for the environment to clean up before completing as success. The issue here is that if a subnet is getting destroyed straight after the cluster is destroyed, some network resources have not finished destroying. This causes the destroy of the subnet to fail as there are still attached network resources. The temporary workaround is to put a 10-minute pause between the cluster and subnet steps on destroy (we needed to add a 10 mins wait in popular regions like us-south, but in au-syd it only needed ~2 mins).
Community Note
Terraform CLI and Terraform IBM Provider Version
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
Panic Output
Expected Behavior
The destroy of the cluster should not complete if there are still attached network resources (subnets) which cannot be destroyed yet.
Actual Behavior
A destroy of subnets being used by the cluster failed because they were still attached to something on the back end.
Steps to Reproduce
terraform apply
terraform destroy
Important Factoids
Workaround we are using:
References
The text was updated successfully, but these errors were encountered: