-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Scaleway: the "scaleway_volume_attachment" takes forever #18709
Comments
Thanks for the bug report. I think This is fixed in #87 - but the branch is missing an approval from second reviewer. I’d be super happy if you’d try out the branch and see if it fixes this issue. |
@vitaliy-zinchenko please open the issue on terraform-providers/terraform-provider-scaleway. |
I am going to close this issue since it was moved to the scaleway provider. Thanks! |
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. |
Terraform Version
terraform -v:
Terraform v0.11.7
Affected Resource(s)
scaleway_volume_attachment
Terraform Configuration Files
provider "scaleway" {
organization = ""
token = ""
region = "ams1"
}
resource "scaleway_ip" "ip" {
server = "${scaleway_server.test.id}"
}
resource "scaleway_server" "test" {
name = "test"
image = "ca9a9340-92e8-4c5f-8ae1-423466f7ef30"
type = "C2S"
}
resource "scaleway_volume" "test" {
name = "test"
size_in_gb = 50
type = "l_ssd"
}
resource "scaleway_volume_attachment" "test" {
server = "${scaleway_server.test.id}"
volume = "${scaleway_volume.test.id}"
}
Debug Output
https://gist.github.com/vitaliy-zinchenko/95d19dc8cfe797d5ca73ec5f79899b8c
Expected Behavior
I would expect to have a running server that got 1 additional volume assigned.
And server back to srunning state.
Actual Behavior
Server is stopped and the Terraform attaching volume forever.
/cc @nicolai86
The text was updated successfully, but these errors were encountered: