You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be timing issue when destroying the resource. The deletion of Express Route Circuit on the Azure side need to wait for the deletion of FastConnect (FC) on the OCI side. It seem to take a few minute for Azure to see that the FC is deleted on OCI. Therefore, it will failed on the first run of terraform destroy. You just need to wait for a few minutes then run terraform destroy again to delete the last resource Express Route Circuit that failed from the previous run. I am wondering if there is a way to pause for a few minutes before delete Express Route Circuit after deletion of FC. The following is the error that I am getting on the firest terraform destroy command:
│ Error: waiting for the deletion of Express Route Circuit: (Name "azure_express_circuit" / Resource Group "azure_oci_test_resources"): Code="ConflictError" Message="The specified dedicated circuit is not in Deprovisioned state. Please initiate the deprovisioning process with your service provider." Details=[]
The text was updated successfully, but these errors were encountered:
There seems to be timing issue when destroying the resource. The deletion of Express Route Circuit on the Azure side need to wait for the deletion of FastConnect (FC) on the OCI side. It seem to take a few minute for Azure to see that the FC is deleted on OCI. Therefore, it will failed on the first run of terraform destroy. You just need to wait for a few minutes then run terraform destroy again to delete the last resource Express Route Circuit that failed from the previous run. I am wondering if there is a way to pause for a few minutes before delete Express Route Circuit after deletion of FC. The following is the error that I am getting on the firest terraform destroy command:
The text was updated successfully, but these errors were encountered: