Describe the bug
I have some VMs that get stuck on the "qmdestroy" task when I try to terraform destroy them. I have stop_on_destroy set to true (tried true/false with same results).
To Reproduce
Create a VM resource (I am using a module I made: https://github.com/kodama-labs/tf-proxmox/tree/master/vm) and terraform destroy it. Terraform gets stuck on "still destroying", and proxmox stays stuck on qmdestroy of that task forever.
Workaround
My workaround is to stop the qmdestroy task and then delete the VM from the proxmox web UI (or delete the vm conf file from the proxmox host)
Additional context
Proxmox output:
()
trying to acquire lock...
OK
Logical volume "vm-105-cloudinit" successfully removed.
trying to acquire lock...
OK
Logical volume "vm-105-disk-0" successfully removed.
Single or clustered Proxmox: Single in clustered mode
Proxmox version: 8.2.4
Provider version (ideally it should be the latest version): 0.66.3
Terraform/OpenTofu version: Terraform 1.9.8
OS (where you run Terraform/OpenTofu from): Arch with Linux 6.6.59
Describe the bug I have some VMs that get stuck on the "qmdestroy" task when I try to
terraform destroythem. I have stop_on_destroy set to true (tried true/false with same results).To Reproduce Create a VM resource (I am using a module I made: https://github.com/kodama-labs/tf-proxmox/tree/master/vm) and
terraform destroyit. Terraform gets stuck on "still destroying", and proxmox stays stuck on qmdestroy of that task forever.Workaround My workaround is to stop the qmdestroy task and then delete the VM from the proxmox web UI (or delete the vm conf file from the proxmox host)
Additional context Proxmox output: