Open terrymandin opened 2 weeks ago
@chanstev , we have received an exemption for the AVM approval process. We will document this know issue in our readme and proceed with deployment. It would still be good to get it resolved at some point.
@terrymandin, This error occurs because VMClusters must be deleted first before the ExaData infrastructure they are associated with can be deleted. Is there a different sort of behaviour you think we should have here to improve the experience?
@eelhomsi, the Terraform should wait for the cluster to be fully deleted before attempting to delete the infrastructure. It seems that the cluster still exists in the background, even when Terraform says it has been succuessfully delete.
At a high level, these are the steps we are following in our Terraform:
Terraform apply:
Terraform destroy
Step 1 of the destroy says the cluster is deleted, even though it seems to still be there. It causes the infra destroy to fail.
Thanks @terrymandin I tried the test myself but deletion seemed to go through ok: Maybe we can discuss with @chanstev in sync tomorrow to understand issue further.
I used AzAPI to deploy Oracle Infrastructure and Cluster resources. When I did a
terraform destroy
I received the following error:To duplicate:
terraform apply
on this example: https://github.com/Azure/terraform-azurerm-avm-ptn-odaa-lz/tree/main/examples/defaultterraform destroy