Infinite Loop on IOPS Change with scaleway_block_volume Resource (Force Replacement Fails)

[Monitob]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Affected Resource(s)

• scaleway_block_volume

Terraform Configuration Files

# Copy-paste the minimal (if possible) terraform configuration to reproduce the bug here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key: https://keybase.io/hashicorp

Debug Output

Panic Output

Expected Behavior

Actual Behavior

When modifying the iops parameter on the scaleway_block_volume resource, Terraform correctly triggers a force replacement. However, instead of successfully replacing the volume, the provider gets stuck in an infinite loop until it hits a timeout.

Terraform detects the change and plans a replacement.

The apply phase enters a loop and never completes.

Eventually, it fails with a timeout.

Steps to Reproduce

resource "scaleway_block_volume" "consumer_storage" {
  ~ id                 = "fr-par-2/<id>" -> (known after apply)
  + instance_volume_id = (known after apply)
  ~ iops               = 5000 -> 15000 # forces replacement
    name               = "demo-storage"
  ~ project_id         = "<id>" -> (known after apply)
  - tags               = [] -> null
  # (3 unchanged attributes hidden)
}

1. terraform apply

Important Factoids

References

• #0000