Comments (6)
@bpg See ticket #1400 . I forgot to mention it explicitly on the ticket but the only diff between the working and non working was the added initialization block
from terraform-provider-proxmox.
Hey @finn0000 👋🏼
It looks like your source VM has some USB device configuration that provider can't parse.
Could you attach output of pvesh get /nodes/pve/qemu/10000/config
from your Proxmox host?
from terraform-provider-proxmox.
Ran into the same issue on my machine, albeit not the exact same issue. Not sure if this needs to be broken out into another issue but I got a similar output:
│ 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.60.0 plugin:
panic: runtime error: index out of range [0] with length 0
goroutine 85 [running]:
github.com/bpg/terraform-provider-proxmox/proxmoxtf/resource/vm.vmUpdate({0x114aee0, 0xc00064f960}, 0xc000742480, {0xeedba0, 0xc0004e3a70})
github.com/bpg/terraform-provider-proxmox/proxmoxtf/resource/vm/vm.go:5108 +0x5765
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).update(0xc000352000, {0x114ae38, 0xc000251560}, 0xc000742480, {0xeedba0, 0xc0004e3a70})
github.com/hashicorp/terraform-plugin-sdk/[email protected]/helper/schema/resource.go:840 +0x119
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).Apply(0xc000352000, {0x114ae38, 0xc000251560}, 0xc0006df520, 0xc000742300, {0xeedba0, 0xc0004e3a70})
github.com/hashicorp/terraform-plugin-sdk/[email protected]/helper/schema/resource.go:947 +0x83a
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*GRPCProviderServer).ApplyResourceChange(0xc00012bc68, {0x114ae38?, 0xc000250600?}, 0xc0006ab900)
github.com/hashicorp/terraform-plugin-sdk/[email protected]/helper/schema/grpc_provider.go:1153 +0xd5c
github.com/hashicorp/terraform-plugin-mux/tf5to6server.v5tov6Server.ApplyResourceChange({{0x1156bf8?, 0xc00012bc68?}}, {0x114ae38, 0xc000250600}, 0x0?)
github.com/hashicorp/[email protected]/tf5to6server/tf5to6server.go:38 +0x54
github.com/hashicorp/terraform-plugin-mux/tf6muxserver.(*muxServer).ApplyResourceChange(0xc000340d20, {0x114ae38?, 0xc0001c54d0?}, 0xc0006ab8b0)
github.com/hashicorp/[email protected]/tf6muxserver/mux_server_ApplyResourceChange.go:36 +0x193
github.com/hashicorp/terraform-plugin-go/tfprotov6/tf6server.(*server).ApplyResourceChange(0xc0003328c0, {0x114ae38?, 0xc000718120?}, 0xc00064e8c0)
github.com/hashicorp/[email protected]/tfprotov6/tf6server/server.go:865 +0x3d0
github.com/hashicorp/terraform-plugin-go/tfprotov6/internal/tfplugin6._Provider_ApplyResourceChange_Handler({0xf78900, 0xc0003328c0}, {0x114ae38, 0xc000718120}, 0xc000743180, 0x0)
github.com/hashicorp/[email protected]/tfprotov6/internal/tfplugin6/tfplugin6_grpc.pb.go:518 +0x1a6
google.golang.org/grpc.(*Server).processUnaryRPC(0xc0001a5200, {0x114ae38, 0xc0006afc20}, {0x1151e60, 0xc000002180}, 0xc0000218c0, 0xc0003f5350, 0x17dafd8, 0x0)
google.golang.org/[email protected]/server.go:1369 +0xdf8
google.golang.org/grpc.(*Server).handleStream(0xc0001a5200, {0x1151e60, 0xc000002180}, 0xc0000218c0)
google.golang.org/[email protected]/server.go:1780 +0xe8b
google.golang.org/grpc.(*Server).serveStreams.func2.1()
google.golang.org/[email protected]/server.go:1019 +0x8b
created by google.golang.org/grpc.(*Server).serveStreams.func2 in goroutine 7
google.golang.org/[email protected]/server.go:1030 +0x125
Error: The terraform-provider-proxmox_v0.60.0 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.
Output of VM using pvesh:
┌──────────┬──────────────────────────────────────────────────────────────────┐
│ key │ value │
╞══════════╪══════════════════════════════════════════════════════════════════╡
│ boot │ order=scsi0;ide2;net0 │
├──────────┼──────────────────────────────────────────────────────────────────┤
│ cores │ 4 │
├──────────┼──────────────────────────────────────────────────────────────────┤
│ cpu │ cputype=qemu64 │
├──────────┼──────────────────────────────────────────────────────────────────┤
│ cpuunits │ 1024 │
├──────────┼──────────────────────────────────────────────────────────────────┤
│ digest │ f6399a75acda3f8808abe2c45554cb236556611f │
├──────────┼──────────────────────────────────────────────────────────────────┤
│ ide2 │ lvm:iso/archlinux-2023.03.01-x86_64.iso,media=cdrom,size=829772K │
├──────────┼──────────────────────────────────────────────────────────────────┤
│ keyboard │ en-us │
├──────────┼──────────────────────────────────────────────────────────────────┤
│ memory │ 4096 │
├──────────┼──────────────────────────────────────────────────────────────────┤
│ name │ TestArch │
├──────────┼──────────────────────────────────────────────────────────────────┤
│ net0 │ virtio=3A:88:CC:4D:B3:A3,bridge=vmbr0,firewall=1 │
├──────────┼──────────────────────────────────────────────────────────────────┤
│ numa │ 0 │
├──────────┼──────────────────────────────────────────────────────────────────┤
│ ostype │ l26 │
├──────────┼──────────────────────────────────────────────────────────────────┤
│ scsi0 │ Data_Pool:vm-102-disk-0,iothread=1,size=32G │
├──────────┼──────────────────────────────────────────────────────────────────┤
│ scsihw │ virtio-scsi-single │
├──────────┼──────────────────────────────────────────────────────────────────┤
│ smbios1 │ uuid=53f4ca60-6dc1-4de7-b4aa-bb9807fe6c82 │
├──────────┼──────────────────────────────────────────────────────────────────┤
│ sockets │ 1 │
├──────────┼──────────────────────────────────────────────────────────────────┤
│ vga │ memory=16,type=std │
├──────────┼──────────────────────────────────────────────────────────────────┤
│ vmgenid │ 60300c1a-921f-4290-8743-e6bc9d5d6856 │
└──────────┴──────────────────────────────────────────────────────────────────┘
It happened to me when I added an ipv4 config to my VM.
from terraform-provider-proxmox.
Hey @micsport13, most likely that's another unrelated issue.
It happened to me when I added an ipv4 config to my VM.
Could you create a new ticket and attach a diff between the new and old configs?
from terraform-provider-proxmox.
@bpg
I apologize for the long answer. Could you tell me how to install the apt install htop package
Could you tell me how to install the apt install htop package
key │ value │
╞═══════════╪══════════════════════════════════════════════════╡
│ agent │ 1 │
├───────────┼──────────────────────────────────────────────────┤
│ bios │ ovmf │
├───────────┼──────────────────────────────────────────────────┤
│ boot │ order=scsi0 │
├───────────┼──────────────────────────────────────────────────┤
│ ciupgrade │ 0 │
├───────────┼──────────────────────────────────────────────────┤
│ cores │ 1 │
├───────────┼──────────────────────────────────────────────────┤
│ digest │ 61882d965139ed38ad1ea7a32bbcd5c8ad89cda6 │
├───────────┼──────────────────────────────────────────────────┤
│ efidisk0 │ local-lvm:base-10000-disk-0,efitype=4m,size=4M │
├───────────┼──────────────────────────────────────────────────┤
│ ide2 │ local-lvm:vm-10000-cloudinit,media=cdrom,size=4M │
├───────────┼──────────────────────────────────────────────────┤
│ machine │ q35 │
├───────────┼──────────────────────────────────────────────────┤
│ memory │ 2048 │
├───────────┼──────────────────────────────────────────────────┤
│ name │ 1.7.4 │
├───────────┼──────────────────────────────────────────────────┤
│ net0 │ virtio=FA:AF:9F:B3:95:50,bridge=vmbr0,firewall=1 │
├───────────┼──────────────────────────────────────────────────┤
│ numa │ 0 │
├───────────┼──────────────────────────────────────────────────┤
│ ostype │ l26 │
├───────────┼──────────────────────────────────────────────────┤
│ scsi0 │ local-lvm:base-10000-disk-1,iothread=1,size=40G │
├───────────┼──────────────────────────────────────────────────┤
│ scsihw │ virtio-scsi-single │
├───────────┼──────────────────────────────────────────────────┤
│ smbios1 │ uuid=562bab96-58ab-45d3-afce-eb09260a8eaa │
├───────────┼──────────────────────────────────────────────────┤
│ sockets │ 1 │
├───────────┼──────────────────────────────────────────────────┤
│ template │ 1 │
├───────────┼──────────────────────────────────────────────────┤
│ usb0 │ spice │
├───────────┼──────────────────────────────────────────────────┤
│ vga │ qxl │
├───────────┼──────────────────────────────────────────────────┤
│ vmgenid │ 5791cdd0-1c77-46e8-a7fd-6024d44c13a4 │
from terraform-provider-proxmox.
Yep, it fails because of usb0="spice"
. I've made a fix, will be in the next release.
Could you tell me how to install the
apt install htop package
Just open root shell to your PVE node:
then run apt install htop
from terraform-provider-proxmox.
Related Issues (20)
- Cannot create volume mount point in LXC HOT 7
- Add support for `proxmox_virtual_environment_file` data source HOT 4
- Terraform VM Creation crashes plugin when adding ipv4 configuration to VM HOT 3
- Context Deadline Exceeded only on certain resources HOT 11
- Using Cloud Init package_upgrade: false HOT 1
- Error: resizing disk: error waiting for VM disk resize: All attempts fail: HOT 5
- After import command or block, unprivileged forces replacement HOT 2
- Live Migration error: retrieving VM 100: the requested resource does not exist HOT 3
- Recommended way to get Packer built VM ID into Terraform control HOT 9
- proxmox_virtual_environment_vm.virtual_machine already exists error HOT 2
- Please add new arguments and attributes to the `proxmox_virtual_environment_vms` data source HOT 2
- Unknown timezone "Europe/Amsterdam" with proxmox_virtual_environment_time HOT 2
- Changing disk size of 'proxmox_virtual_environment_container' forces replacement HOT 4
- proxmox_virtual_environment_download_file can't read metadata HOT 2
- CloudImage size changes forces replacement of VM HOT 2
- proxmox_virtual_environment_vm forces replacement by unchanged initialization.user_account.keys HOT 3
- A question about documentation related to the proxmox_virtual_environment_container resource
- Error listing files from datastore using API Token as credentials HOT 2
- Unable to download iso (OpenTofu) HOT 2
- proxmox_virtual_environment_network_linux_bridge additional config
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from terraform-provider-proxmox.