You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Not sure if that is desired behavior but I run in to an error when trying to persist ip address to the secondary network device, when primary one needs to stay without configuration.
To Reproduce
Steps to reproduce the behavior:
Create a container resource with multiple network devices and create initialization config with at least one empty ip_config.
Run terraform plan
See error
module.lxc_debian_gateway.proxmox_virtual_environment_container.lxc_container: Modifying... [id=4000]
╷
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the plugin6.(*GRPCProvider).ApplyResourceChange call. The plugin logs may contain more details.
╵
Stack trace from the terraform-provider-proxmox_v0.43.3 plugin:
panic: interface conversion: interface {} is nil, not map[string]interface {}
goroutine 81 [running]:
github.com/bpg/terraform-provider-proxmox/proxmoxtf/resource.containerUpdate({0x106d7f0, 0xc000534930}, 0xc000417100, {0xe38340?, 0xc000015710?})
github.com/bpg/terraform-provider-proxmox/proxmoxtf/resource/container.go:2529 +0x3586
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).update(0xc0002f49a0, {0x106d748, 0xc000627110}, 0xd?, {0xe38340, 0xc000015710})
github.com/hashicorp/terraform-plugin-sdk/v2@v2.31.0/helper/schema/resource.go:812 +0x11b
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).Apply(0xc0002f49a0, {0x106d748, 0xc000627110}, 0xc0000c2000, 0xc000416e00, {0xe38340, 0xc000015710})
github.com/hashicorp/terraform-plugin-sdk/v2@v2.31.0/helper/schema/resource.go:919 +0x83a
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*GRPCProviderServer).ApplyResourceChange(0xc0001173f8, {0x106d748?, 0xc000626f60?}, 0xc0006283c0)
github.com/hashicorp/terraform-plugin-sdk/v2@v2.31.0/helper/schema/grpc_provider.go:1074 +0xdbc
github.com/hashicorp/terraform-plugin-mux/tf5to6server.v5tov6Server.ApplyResourceChange({{0x1074e20?, 0xc0001173f8?}}, {0x106d748, 0xc000626f60}, 0x0?)
github.com/hashicorp/terraform-plugin-mux@v0.13.0/tf5to6server/tf5to6server.go:37 +0x54
github.com/hashicorp/terraform-plugin-mux/tf6muxserver.(*muxServer).ApplyResourceChange(0x106d780?, {0x106d748?, 0xc000626c60?}, 0xc000628370)
github.com/hashicorp/terraform-plugin-mux@v0.13.0/tf6muxserver/mux_server_ApplyResourceChange.go:36 +0x193
github.com/hashicorp/terraform-plugin-go/tfprotov6/tf6server.(*server).ApplyResourceChange(0xc00026b900, {0x106d748?, 0xc000626240?}, 0xc0000d8000)
github.com/hashicorp/terraform-plugin-go@v0.20.0/tfprotov6/tf6server/server.go:857 +0x56b
github.com/hashicorp/terraform-plugin-go/tfprotov6/internal/tfplugin6._Provider_ApplyResourceChange_Handler({0xeb7a40?, 0xc00026b900}, {0x106d748, 0xc000626240}, 0xc000416280, 0x0)
github.com/hashicorp/terraform-plugin-go@v0.20.0/tfprotov6/internal/tfplugin6/tfplugin6_grpc.pb.go:503 +0x169
google.golang.org/grpc.(*Server).processUnaryRPC(0xc00025e1e0, {0x106d748, 0xc0006261b0}, {0x10733d0, 0xc0000fe000}, 0xc00062c000, 0xc0003bec30, 0x167ed98, 0x0)
google.golang.org/grpc@v1.60.0/server.go:1372 +0xe03
google.golang.org/grpc.(*Server).handleStream(0xc00025e1e0, {0x10733d0, 0xc0000fe000}, 0xc00062c000)
google.golang.org/grpc@v1.60.0/server.go:1783 +0xfec
google.golang.org/grpc.(*Server).serveStreams.func2.1()
google.golang.org/grpc@v1.60.0/server.go:1016 +0x59
created by google.golang.org/grpc.(*Server).serveStreams.func2 in goroutine 11
google.golang.org/grpc@v1.60.0/server.go:1027 +0x115
Error: The terraform-provider-proxmox_v0.43.3 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.
Please also provide a minimal Terraform configuration that reproduces the issue.
Thanks!
It is very similar to #918. I guess there are plenty of similar use cases where checks for empty blocks are missing.
A fair warning though, the empty sections will stay in the terraform state, but won't be reflected in any way in the VM state in PVE, so the TF plan will always complain that there is a change, and will try to apply that empty section every time (which will be no-op after the fix).
Describe the bug
Not sure if that is desired behavior but I run in to an error when trying to persist ip address to the secondary network device, when primary one needs to stay without configuration.
To Reproduce
Steps to reproduce the behavior:
Create a container resource with multiple network devices and create initialization config with at least one empty ip_config.
Run terraform plan
See error
Expected behavior
Network device should be initialized with empty static ip
TF_LOG=DEBUG terraform apply
):The text was updated successfully, but these errors were encountered: