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
When a provider becomes offline/inactive, one normally would want to use terraform destroy/terraform apply to close the active deployment and redeploy it elsewhere.
Current Behaviour
Currently, what happens when one tries to run terraform destroy is a long wait time which results in "connect: operation timed out".
akash_deployment.my_deployment: Refreshing state... [id=XXXXXX:1:1:XXXXXXXXXXX
╷
│ Error: Error: Get "https://provider.hurricane.akash.pub:8443/lease/XXXXX/1/1/status": dial tcp 216.239.32.21:8443: connect: operation timed out
Expected Behaviour
I would expect that the terraform provider would understand - after a reasonable amount of tries - that the provider is no longer online and therefore ( since a destroy command was requested ) proceed with closing the deployment.
The text was updated successfully, but these errors were encountered:
When a provider becomes offline/inactive, one normally would want to use terraform destroy/terraform apply to close the active deployment and redeploy it elsewhere.
Current Behaviour
Currently, what happens when one tries to run
terraform destroy
is a long wait time which results in "connect: operation timed out".Expected Behaviour
I would expect that the terraform provider would understand - after a reasonable amount of tries - that the provider is no longer online and therefore ( since a destroy command was requested ) proceed with closing the deployment.
The text was updated successfully, but these errors were encountered: