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

Zone not set for sbs_volumes in ListServers, Causing Terraform Errors #2273

Open
0xbe7a opened this issue Oct 23, 2024 · 1 comment
Open
Assignees
Labels
bug Something isn't working instance Instance issues, bugs and feature requests priority:highest Bugs filled by customers, security issues

Comments

@0xbe7a
Copy link

0xbe7a commented Oct 23, 2024

The sbs_volumes do not have the Volumes.[].Zone set when using ListServers. This conflicts with the behavior described in https://github.com/scaleway/scaleway-sdk-go/blob/master/api/instance/v1/instance_sdk.go#L1503, as the client interprets this as "default."

To reproduce the issue:

  1. Create a server with attached sbs_volumes.
  2. Run scw instance server list --json.
  3. Observe that the zone is not set for the attached sbs_volumes.

This causes issues, such as breaking the Terraform state update when using multiple zones. The Terraform provider attempts to query the volume using the default region instead of the correct volume region for sbs_volumes, resulting in the following error: │ Error: failed to read instance volume 8fa94ad1-[redacted]: scaleway-sdk-go: resource volume with ID 8fa94ad1-[redacted] is not found.

@remyleone remyleone added bug Something isn't working instance Instance issues, bugs and feature requests priority:highest Bugs filled by customers, security issues labels Oct 23, 2024
@Codelax
Copy link
Member

Codelax commented Oct 24, 2024

Hi ! Thanks for reporting this issue.
I forwarded the issue to the instance team. For now I will circumvent this in Terraform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working instance Instance issues, bugs and feature requests priority:highest Bugs filled by customers, security issues
Projects
None yet
Development

No branches or pull requests

3 participants