-
Notifications
You must be signed in to change notification settings - Fork 512
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
Kernal Panic - interface conversion: interface {} is string, not float64 #903
Comments
Almost the same thing for me. Using Version 2.9.11 of the plugin, I got the following message:
Same thing, after having upgraded to Version 2.9.14 ... |
I'm getting the same error. In my case, the same terraform code works without error when targetting proxmox ve 7 instances but fails when targetting proxmox ve 8 instances. |
You can check these issues as well. I am currently using @TheGameProfi release and it works fine besides an issue with a cloud init drive that he and a few others are working on. There is also a discord https://discord.gg/vn5sbuNkfc |
It seems a solution was found on #863 #863 (comment) in november, shocked this hasnt been addressed in the plugin yet? |
@pyrosyndicate it has been addressed in the repo but we need to make a new release you can use https://registry.terraform.io/providers/TheGameProfi/proxmox/2.9.16 |
The fork mentioned is also broken. Cloud init drives on template break the deploy in a similar fashion so not a solution. |
Yeah the disks are broken we are still working on that |
Same thing, the weekend we did an update from 8.0 to 8.1.4 it the stopped working same error. |
At the same problem |
Experiencing same issue. Right after update to 8.1.4. Recent rc version works but missing configuration options which were crucial in my case. |
Can anyone reproduce this issue with the 3.0.1-rc1 release? I didn't run into it when I was testing, and I'm not sure if it was fixed between 2.9.14 and 3.0.1-rc1 or if there's some subtle difference between the example posted in this report and the example I am using. Aside from the disk -> disks change, the two examples really look pretty similar. |
@hestiahacker, this panic is fixed in the new version. This was an issue in the underlying proxmox-go-api project Telmate/proxmox-api-go#285 |
This issue is stale because it has been open for 60 days with no activity. Please update the provider to the latest version and, in the issue persist, provide full configuration and debug logs |
This issue was closed because it has been inactive for 5 days since being marked as stale. |
|
You must add the proper version on your provider file
Then just update it
|
I am trying to build a simple VM within proxmox using a simple sample script.
maintf.txt
varstf.txt
Issue in console from client running the code is:
proxmox_vm_qemu.testserver[0]: Creating...
proxmox_vm_qemu.testserver[0]: Still creating... [10s elapsed]
proxmox_vm_qemu.testserver[0]: Still creating... [20s elapsed]
╷
│ Error: Request cancelled
│
│ with proxmox_vm_qemu.testserver[0],
│ on main.tf line 33, in resource "proxmox_vm_qemu" "testserver":
│ 33: resource "proxmox_vm_qemu" "testserver" {
│
│ The plugin.(*GRPCProvider).ApplyResourceChange request was cancelled.
╵
Stack trace from the terraform-provider-proxmox_v2.9.14 plugin:
panic: interface conversion: interface {} is string, not float64
goroutine 32 [running]:
github.com/Telmate/proxmox-api-go/proxmox.NewConfigQemuFromApi(0xc0007b8718, 0x189e92a?)
github.com/Telmate/[email protected]/proxmox/config_qemu.go:584 +0x4605
github.com/Telmate/terraform-provider-proxmox/proxmox.resourceVmQemuCreate(0xc000614a00, {0x1767860?, 0xc0004b4d20})
github.com/Telmate/terraform-provider-proxmox/proxmox/resource_vm_qemu.go:972 +0x2c4d
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).create(0x19d8be0?, {0x19d8be0?, 0xc0001bd4d0?}, 0xd?, {0x1767860?, 0xc0004b4d20?})
github.com/hashicorp/terraform-plugin-sdk/[email protected]/helper/schema/resource.go:695 +0x178
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).Apply(0xc0003767e0, {0x19d8be0, 0xc0001bd4d0}, 0xc0006341a0, 0xc000614280, {0x1767860, 0xc0004b4d20})
github.com/hashicorp/terraform-plugin-sdk/[email protected]/helper/schema/resource.go:837 +0xa85
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*GRPCProviderServer).ApplyResourceChange(0xc000410b70, {0x19d8be0?, 0xc0001bd3b0?}, 0xc00041e2d0)
github.com/hashicorp/terraform-plugin-sdk/[email protected]/helper/schema/grpc_provider.go:1021 +0xe8d
github.com/hashicorp/terraform-plugin-go/tfprotov5/tf5server.(*server).ApplyResourceChange(0xc000000460, {0x19d8be0?, 0xc0001bc540?}, 0xc0001c6070)
github.com/hashicorp/[email protected]/tfprotov5/tf5server/server.go:818 +0x574
github.com/hashicorp/terraform-plugin-go/tfprotov5/internal/tfplugin5._Provider_ApplyResourceChange_Handler({0x186d600?, 0xc000000460}, {0x19d8be0, 0xc0001bc540}, 0xc0001c6000, 0x0)
github.com/hashicorp/[email protected]/tfprotov5/internal/tfplugin5/tfplugin5_grpc.pb.go:385 +0x170
google.golang.org/grpc.(*Server).processUnaryRPC(0xc0000361e0, {0x19dc840, 0xc0004824e0}, 0xc000422000, 0xc000428bd0, 0x1e95900, 0x0)
google.golang.org/[email protected]/server.go:1336 +0xd23
google.golang.org/grpc.(*Server).handleStream(0xc0000361e0, {0x19dc840, 0xc0004824e0}, 0xc000422000, 0x0)
google.golang.org/[email protected]/server.go:1704 +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-proxmox_v2.9.14 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.
and error log is attached:
terraform-plugin-proxmox.log
Interestingly the VM is being created and does boot succesfully. I have not attempted to login yet. but Terraform is not aware of this and a plan shows as the vm not existing.
The text was updated successfully, but these errors were encountered: