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

Error: The terraform-provider-azurerm_v3.7.0_x5 plugin crashed! when update azurerm_kubernetes_cluster #16967

Closed
1 task done
nigelis opened this issue May 26, 2022 · 5 comments · Fixed by #17005
Closed
1 task done

Comments

@nigelis
Copy link

nigelis commented May 26, 2022

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

AzureRM Provider Version

3.7.0

Affected Resource(s)/Data Source(s)

azurerm_kubernetes_cluster

Terraform Configuration Files

resource "azurerm_kubernetes_cluster" "main" {
  ...

  lifecycle {
    ignore_changes = [
      private_cluster_public_fqdn_enabled,
      run_command_enabled,
    ]
  }
}

Debug Output/Panic Output

https://gist.github.com/nigelis/ef737a98ec2b3a7cf956435b2d5ee0a2

Expected Behaviour

The Kubernetes cluster is updated successfully.

Actual Behaviour

Crash.

Steps to Reproduce

No response

Important Factoids

No response

References

No response

@nigelis nigelis added the bug label May 26, 2022
@github-actions github-actions bot removed the bug label May 26, 2022
@nigelis
Copy link
Author

nigelis commented May 26, 2022

The Kubernetes cluster is created by CLI last year.
When I import it into terraform, the value of fields run_command_enabled and private_cluster_public_fqdn_enabled is null.
Now, I can not update the cluster via terraform, even ignore these two fields or declare the fields to default value explicitly.

@sanglt
Copy link

sanglt commented May 27, 2022

I have the same error:

│ The plugin.(*GRPCProvider).ApplyResourceChange request was cancelled.
╵

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

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

goroutine 98 [running]:
github.com/hashicorp/terraform-provider-azurerm/internal/services/containers.resourceKubernetesClusterUpdate(0xc0001c0d00, {0x54f1ba0?, 0xc000409c00})
	github.com/hashicorp/terraform-provider-azurerm/internal/services/containers/kubernetes_cluster_resource.go:1372 +0x1755
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).update(0xc000d00450?, {0x6568b08?, 0xc00267b1c0?}, 0x24?, {0x54f1ba0?, 0xc000409c00?})
	github.com/hashicorp/terraform-plugin-sdk/v2@v2.10.1/helper/schema/resource.go:363 +0x178
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).Apply(0xc000868a80, {0x6568b08, 0xc00267b1c0}, 0xc00127b930, 0xc0000a5f80, {0x54f1ba0, 0xc000409c00})
	github.com/hashicorp/terraform-plugin-sdk/v2@v2.10.1/helper/schema/resource.go:475 +0x53a
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*GRPCProviderServer).ApplyResourceChange(0xc0003755f0, {0x6568b08, 0xc00267b1c0}, 0xc001376230)
	github.com/hashicorp/terraform-plugin-sdk/v2@v2.10.1/helper/schema/grpc_provider.go:977 +0xd8a
github.com/hashicorp/terraform-plugin-go/tfprotov5/tf5server.(*server).ApplyResourceChange(0xc0000a5180, {0x6568bb0?, 0xc0018be1e0?}, 0xc002088000)
	github.com/hashicorp/terraform-plugin-go@v0.5.0/tfprotov5/tf5server/server.go:603 +0x2ad
github.com/hashicorp/terraform-plugin-go/tfprotov5/internal/tfplugin5._Provider_ApplyResourceChange_Handler({0x5a59660?, 0xc0000a5180}, {0x6568bb0, 0xc0018be1e0}, 0xc00150a060, 0x0)
	github.com/hashicorp/terraform-plugin-go@v0.5.0/tfprotov5/internal/tfplugin5/tfplugin5_grpc.pb.go:380 +0x170
google.golang.org/grpc.(*Server).processUnaryRPC(0xc000221180, {0x6579c50, 0xc00017a900}, 0xc0019f8000, 0xc000be1b90, 0xa488860, 0x0)
	google.golang.org/grpc@v1.39.0/server.go:1292 +0xc6f
google.golang.org/grpc.(*Server).handleStream(0xc000221180, {0x6579c50, 0xc00017a900}, 0xc0019f8000, 0x0)
	google.golang.org/grpc@v1.39.0/server.go:1617 +0xa1b
google.golang.org/grpc.(*Server).serveStreams.func1.2()
	google.golang.org/grpc@v1.39.0/server.go:940 +0x98
created by google.golang.org/grpc.(*Server).serveStreams.func1
	google.golang.org/grpc@v1.39.0/server.go:938 +0x28a

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

This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.

@tombuildsstuff
Copy link
Contributor

@stephybun would you mind taking a look into this one?

@github-actions
Copy link

github-actions bot commented Jun 3, 2022

This functionality has been released in v3.9.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

github-actions bot commented Jul 4, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants