Terraform - terraform-provider-azurerm_v4.10.0_x5 plugin crashed!

Terraform Providers
1

As of yesterday 25th Jan 2025 I started seeing the below error when running my Terraform scripts via Azure devOps pipeline…

“The plugin encountered an error, and failed to respond to the

│ plugin.(*GRPCProvider).ReadResource call. The plugin logs may contain more.”

github.com/hashicorp/terraform-plugin-mux/tf5muxserver.(*muxServer).ReadDataSource(0xc0001edb00, {0x8a982b8?, 0xc00151e930?}, 0xc00151e8d0)

github.com/hashicorp/terraform-plugin-mux@v0.17.0/tf5muxserver/mux_server_ReadDataSource.go:36 +0x193

github.com/hashicorp/terraform-plugin-go/tfprotov5/tf5server.(*server).ReadDataSource(0xc0012da0a0, {0x8a982b8?, 0xc00151e120?}, 0xc0030175e0)

github.com/hashicorp/terraform-plugin-go@v0.25.0/tfprotov5/tf5server/server.go:688 +0x27d

github.com/hashicorp/terraform-plugin-go/tfprotov5/internal/tfplugin5._Provider_ReadDataSource_Handler({0x7f7f9a0, 0xc0012da0a0}, {0x8a982b8, 0xc00151e120}, 0xc003fc0880, 0x0)

github.com/hashicorp/terraform-plugin-go@v0.25.0/tfprotov5/internal/tfplugin5/tfplugin5_grpc.pb.go:665 +0x1a6

google.golang.org/grpc.(*Server).processUnaryRPC(0xc0015d4200, {0x8a982b8, 0xc00151e090}, {0x8ac6ba0, 0xc00131e000}, 0xc0015b57a0, 0xc001d93e00, 0xe1798a0, 0x0)

google.golang.org/grpc@v1.67.1/server.go:1394 +0xe49

google.golang.org/grpc.(*Server).handleStream(0xc0015d4200, {0x8ac6ba0, 0xc00131e000}, 0xc0015b57a0)

google.golang.org/grpc@v1.67.1/server.go:1805 +0xe8b

google.golang.org/grpc.(*Server).serveStreams.func2.1()

google.golang.org/grpc@v1.67.1/server.go:1029 +0x8b

created by google.golang.org/grpc.(*Server).serveStreams.func2 in goroutine 20

google.golang.org/grpc@v1.67.1/server.go:1040 +0x125

Error: The terraform-provider-azurerm_v4.10.0_x5 plugin crashed!

2

To fix the issue…

Commented out the last 5 Terraform blocks I added before the issue occured and ran Terraform; init, plan and apply which destroyted the Azure Resource.

Next I un-commented code and ran Terraform; init, plan and apply via Azure devOps and the provider issue was resolved. Being honsest I don’t understand what went wrong.