Skip to content
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

Cannot close a deployment when provider is inactive/offline #39

Open
GoncaloPT opened this issue Aug 24, 2023 · 0 comments
Open

Cannot close a deployment when provider is inactive/offline #39

GoncaloPT opened this issue Aug 24, 2023 · 0 comments

Comments

@GoncaloPT
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant