memory crash terraform-provider-azurerm_v3.61.0_x5.exe

[waylew50]

Is there an existing issue for this?

• I have searched the existing issues

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

1.5.1

AzureRM Provider Version

3.61.0

Affected Resource(s)/Data Source(s)

data.azurerm_virtual_machine_scale_set

Terraform Configuration Files

data "azurerm_virtual_machine_scale_set" "WriterBuildAgent" {
  name                = var.vmss_build_agents["writer"].name
  resource_group_name = var.vmss_build_agents["writer"].resource_group_name
}

Debug Output/Panic Output

Stack trace from the terraform-provider-azurerm_v3.61.0_x5.exe plugin:

panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x5a6a25a]

goroutine 117 [running]:
github.com/hashicorp/terraform-provider-azurerm/internal/services/compute.getVirtualMachineScaleSetVMConnectionInfo({0x832f608, 0xc0023ac2a0}, {0xc002525270, 0x1, 0xd18c2e2800?}, {0xc002394450, 0x12}, {0xc0023a2340, 0x1a}, {0xc0
01b83f96, ...}, ...)
        github.com/hashicorp/terraform-provider-azurerm/internal/services/compute/virtual_machine_scale_set_data_source.go:235 +0x79a
github.com/hashicorp/terraform-provider-azurerm/internal/services/compute.dataSourceVirtualMachineScaleSetRead(0x0?, {0x6e37240?, 0xc001a43400?})
        github.com/hashicorp/terraform-provider-azurerm/internal/services/compute/virtual_machine_scale_set_data_source.go:184 +0xf0a
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).read(0x832f640?, {0x832f640?, 0xc0013e8b10?}, 0xd?, {0x6e37240?, 0xc001a43400?})
        github.com/hashicorp/terraform-plugin-sdk/[email protected]/helper/schema/resource.go:712 +0x178
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).ReadDataApply(0xc000b6c1c0, {0x832f640, 0xc0013e8b10}, 0xc000299b00, {0x6e37240, 0xc001a43400})
        github.com/hashicorp/terraform-plugin-sdk/[email protected]/helper/schema/resource.go:943 +0x145
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*GRPCProviderServer).ReadDataSource(0xc00187ea38, {0x832f640?, 0xc0013e89f0?}, 0xc001b40840)
        github.com/hashicorp/terraform-plugin-sdk/[email protected]/helper/schema/grpc_provider.go:1195 +0x38f
github.com/hashicorp/terraform-plugin-go/tfprotov5/tf5server.(*server).ReadDataSource(0xc0008f5d60, {0x832f640?, 0xc002c1e180?}, 0xc0005b60a0)
        github.com/hashicorp/[email protected]/tfprotov5/tf5server/server.go:658 +0x403
github.com/hashicorp/terraform-plugin-go/tfprotov5/internal/tfplugin5._Provider_ReadDataSource_Handler({0x761f380?, 0xc0008f5d60}, {0x832f640, 0xc002c1e180}, 0xc0019d8000, 0x0)
        github.com/hashicorp/[email protected]/tfprotov5/internal/tfplugin5/tfplugin5_grpc.pb.go:421 +0x170
google.golang.org/grpc.(*Server).processUnaryRPC(0xc000260000, {0x833faa0, 0xc001b7c000}, 0xc000826000, 0xc001bf6450, 0xc985710, 0x0)
        google.golang.org/[email protected]/server.go:1340 +0xd23
google.golang.org/grpc.(*Server).handleStream(0xc000260000, {0x833faa0, 0xc001b7c000}, 0xc000826000, 0x0)
        google.golang.org/[email protected]/server.go:1713 +0xa2f
google.golang.org/grpc.(*Server).serveStreams.func1.2()
        google.golang.org/[email protected]/server.go:965 +0x98
created by google.golang.org/grpc.(*Server).serveStreams.func1
        google.golang.org/[email protected]/server.go:963 +0x28a

Error: The terraform-provider-azurerm_v3.61.0_x5.exe plugin crashed!

Expected Behaviour

No response

Actual Behaviour

No response

Steps to Reproduce

1 terraform plan

Important Factoids

os windows 11

References

No response

[github-actions]

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.