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
The debug output is difficult to upload to Gist because it contains confidential information including the api secret key.
Please let us know how to do this so that we can send you the logs encrypted or masked if necessary.
Here is an excerpt from the relevant part of the debug output(Some information is masked).
Successful attachment of the volume to the instance.
Actual Behavior
The following error occurs.
Error: Error waiting for volume (63bbf49d-b142-4905-90db-2c6eb9fe292f) be attached: unexpected state 'reserved', wanted target 'in-use'. last error: %!s(<nil>)
After the error occurs, checking the status on the portal site, it appears to be attached normally. However, there is a discrepancy between the tfstate and the actual state, which cannot be managed as terraform.
Steps to Reproduce
Just run terraform apply.
It does not occur every time, but rather once every 3 to 4 times, according to our experience.
Terraform Version
terraform:1.9.5
ecl provider:2.9.0
Affected Resource(s)
Terraform Configuration Files
main.tf
compute_instance.tf
storage.tf
Debug Output
The debug output is difficult to upload to Gist because it contains confidential information including the api secret key.
Please let us know how to do this so that we can send you the logs encrypted or masked if necessary.
Here is an excerpt from the relevant part of the debug output(Some information is masked).
Panic Output
N/A
Expected Behavior
Successful attachment of the volume to the instance.
Actual Behavior
The following error occurs.
After the error occurs, checking the status on the portal site, it appears to be attached normally. However, there is a discrepancy between the tfstate and the actual state, which cannot be managed as terraform.
Steps to Reproduce
Just run
terraform apply
.It does not occur every time, but rather once every 3 to 4 times, according to our experience.
Looking at line 99 of the code (https://github.com/nttcom/terraform-provider-ecl/blob/master/ecl/resource_ecl_compute_volume_attach_v2.go), The volume attach create seems to expect a state transition from “available” to “attaching” to “in-use”, but in fact there is a timing when the state becomes “reserved”, which seems to be the cause of this issue.
I cannot suggest a code fix because I do not know the exact state transition at volume attach, but I would very much appreciate a fix.
Important Factoids
N/A
References
N/A
The text was updated successfully, but these errors were encountered: