azurerm_netapp_volume broken in 2.49

[nshores]

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 "me too" comments, 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 0.13.5 - AzureRM Version 2.49

Affected Resource(s)

• azurerm_netapp_volume

Terraform Configuration Files

resource "azurerm_netapp_volume" "netapp-volume-1" {
  lifecycle {
    prevent_destroy = false
  }

  name                  = var.volume_name_1
  account_name          = azurerm_netapp_account.netapp.name
  location              = "westus"
  resource_group_name   = var.resource_group_name
  pool_name             = azurerm_netapp_pool.netapp.name
  volume_path           = var.volume_path_1
  subnet_id             = var.subnet_id
  service_level         = var.service_level
  storage_quota_in_gb   = var.storage_quota_in_gb_1
}

Debug Output

https://gist.github.com/nshores/5ecd47ddc351fff1030256e557596850

Expected Behaviour

azurerm_netapp_volume should refresh state of current volumes.

Actual Behaviour

Crash when refreshing state of volume.

Steps to Reproduce

1. terraform plan

Important Factoids

Rolling back to 2.46.1 fixes the issue.

References

#10610 appears to be the breaking change. @paulomarquesc

[paulomarquesc]

I'm looking into this.

[paulomarquesc]

@nshores , can you provide more details? Based on your repro steps I could not reproduce your issue, this is what I've done:

1. Executed an init, plan and apply to build up
2. Re-run plan after all was created and got no changes as result

This is the screenshot of running plan being executed the second time:

This is my testing TF code:

https://gist.github.com/paulomarquesc/961d5b25874001b23451010160be6a91

[paulomarquesc]

I was actually able to reproduce it, if using the same 2.49.0 it works fine, but I retried my steps using 2.48.0, then upgraded (init with -upgrade) to 2.49.0 and when executed the plan with the new version I could reproduce it.

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!