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

Problem deleting block volume on Openstack #4110

Closed
elliottsam opened this issue Nov 30, 2015 · 4 comments · Fixed by #4204
Closed

Problem deleting block volume on Openstack #4110

elliottsam opened this issue Nov 30, 2015 · 4 comments · Fixed by #4204
Labels

Comments

@elliottsam
Copy link

I am seeing the following error when trying to remove a secondary volume that has been added, running Terraform 0.6.6, it will eventually complete successfully, but this can take 20-30mins.

2 error(s) occurred:

* openstack_blockstorage_volume_v1.ms.1: Error deleting OpenStack volume: Expected HTTP response code [202 204] when accessing [DELETE ...], but got 400 instead
{"badRequest": {"message": "Invalid volume: Volume status must be available or error, but current status is: deleting", "code": 400}}
* openstack_blockstorage_volume_v1.ms.2: Error deleting OpenStack volume: Expected HTTP response code [202 204] when accessing [DELETE ...], but got 400 instead
{"badRequest": {"message": "Invalid volume: Volume status must be available or error, but current status is: deleting", "code": 400}}
@jtopjian
Copy link
Contributor

jtopjian commented Dec 2, 2015

Sorry for the delay with this. In order for this error to occur, the volume must already be in a state of deleting at the time the Delete request happened, which is odd.

Do you have an example Terraform configuration that can reproduce this? Is there another way that can trigger or reproduce this situation?

@jtopjian
Copy link
Contributor

jtopjian commented Dec 3, 2015

Coincidentally enough, I discovered how to create this issue by working on #4090. I have a fix for this, and since the fix is part of the fix for #4090, I'll create a single PR to resolve both that issue and this one.

@jtopjian
Copy link
Contributor

jtopjian commented Dec 8, 2015

@elliottsam I decided to open a PR that targets this issue specifically. #4204 should fix this. If you're able to test it out, let me know how it works.

@ghost
Copy link

ghost commented Apr 29, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants