qm destroy looking in the wrong place?

[dpearceFL]

All at the command line... I have to jump through these hoops because "qm create" has no way to target a specific host in a cluster.

1. So I run "qm create 1001" on HOST1.
2. Then I run "qm migrate 1001 HOST2" on HOST1.
3. Then I run "qm destroy 1001" on HOST1
4. And I get this message: "Configuration file 'nodes/HOST2/qemu-server/1000.conf' does not exist"
5. The conf file exists in /etc/pve/nodes/HOST1/qemu-server
6. If I manually mv the configuration file to HOST1 it will delete.

So it looks like "qm destroy" is looking in the original location for the configuration file. If I move the config file to the HOST1 folder, "qm destroy" works.

Looks like a bug in "qm migrate" or "qm destroy".

 

[bbgeek17]

"qm create" has no way to target a specific host in a cluster.

qm is local to the node you are running on. If you need to target a non-local node you can either run over ssh or utilize pvesh ( https://pve.proxmox.com/pve-docs/api-viewer/#/nodes/{node}/qemu )

Then I run "qm destroy 1001" on HOST1

qm is local and is only aware of _local_ config.

Looks like a bug in "qm migrate" or "qm destroy".

Its FAD. If you run "qm list" you will see that it only shows VMs local to the node, those are the ones you can operate on.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[dpearceFL]

You are totally right!! I wound up SSHing into the node that I wanted the VM created on and all is well.