panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x6b8aadc]

[mikemadeja]

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 and review the contribution guide to help.

Terraform Version

1.8.2

AzureRM Provider Version

3.102

Affected Resource(s)/Data Source(s)

azurerm_key_vault_access_policy, azurerm_web_pubsub_network_acl

Terraform Configuration Files

My module is pretty complex. I will try to reproduce it with a similar one...

Debug Output/Panic Output

`
│ Error: Plugin did not respond
│ 
│   with module.webpubsub.module.keyvault_accesspolicy_wps[0].azurerm_key_vault_access_policy.key_vault_access_policies,
│   on .terraform/modules/webpubsub.keyvault_accesspolicy_wps/resource-akv-accesspolicy.tf line 1, in resource "azurerm_key_vault_access_policy" "key_vault_access_policies":
│    1: resource "azurerm_key_vault_access_policy" "key_vault_access_policies" {
│ 
│ The plugin encountered an error, and failed to respond to the
│ plugin.(*GRPCProvider).ApplyResourceChange call. The plugin logs may
│ contain more details.
╵
╷
│ Error: Plugin did not respond
│ 
│   with module.webpubsub.azurerm_web_pubsub_network_acl.webpubsub[0],
│   on .terraform/modules/webpubsub/main.tf line 76, in resource "azurerm_web_pubsub_network_acl" "webpubsub":
│   76: resource "azurerm_web_pubsub_network_acl" "webpubsub" {
│ 
│ The plugin encountered an error, and failed to respond to the
│ plugin.(*GRPCProvider).ApplyResourceChange call. The plugin logs may
│ contain more details.
╵
╷
│ Error: Plugin did not respond
│ 
│   with module.webpubsub.azurerm_web_pubsub_custom_certificate.custom_domain[0],
│   on .terraform/modules/webpubsub/resources-dns.tf line 1, in resource "azurerm_web_pubsub_custom_certificate" "custom_domain":
│    1: resource "azurerm_web_pubsub_custom_certificate" "custom_domain" {
│ 
│ The plugin encountered an error, and failed to respond to the
│ plugin.(*GRPCProvider).ApplyResourceChange call. The plugin logs may
│ contain more details.
╵

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

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x6b8aadc]

goroutine 352 [running]:
github.com/hashicorp/terraform-provider-azurerm/internal/services/signalr.resourceWebPubsubNetworkACLCreateUpdate(0xc001a3c180, {0x76d02e0?, 0xc0015a5200})
	github.com/hashicorp/terraform-provider-azurerm/internal/services/signalr/web_pubsub_network_acl_resource.go:168 +0x55c
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).create(0x8eee870?, {0x8eee870?, 0xc00270ffb0?}, 0xd?, {0x76d02e0?, 0xc0015a5200?})
	github.com/hashicorp/terraform-plugin-sdk/[email protected]/helper/schema/resource.go:766 +0x163

`

Expected Behaviour

It should assing the KeyVault RBAC and setup WPS ACL.

Actual Behaviour

It crashes with the above error.

Steps to Reproduce

terraform apply

Important Factoids

No response

References

No response

[tombuildsstuff]

@klausgh4836 @Sanorikos FWIW the Lighthouse related crash is fixed by #25861 which has been merged and will ship in this weeks release - however note the Lighthouse related crash (in your comments) is a different crash to the issue description (which is a crash in webpubsub) - and as such I'm going to mark your comments as off-topic to keep this issue focused on the webpubsub issue.

[mikemadeja]

Thanks @tombuildsstuff, I appreciate it.

[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.