[pve-devel] Handling 'path' requests during VM deletion

Andrei Perapiolkin andrei.perepiolkin at open-e.com
Thu Aug 7 23:34:02 CEST 2025


Hi,

VM deletion retries 'path'/'free_image' for already-removed volumes; 
expected plugin behavior on missing volumes is unclear.

When deleting a VM with multiple attached volumes, Proxmox deletes 
volumes sequentially (one at a time) and
updates the VM record only after all deletions complete.
If a volume deletion fails mid-process (e.g., network error), the VM 
record is not updated even though some volumes may have been 
successfully removed.
A subsequent delete attempt repeats all operations, including 'path' 
(and 'free_image') calls for volumes that were already deleted.


What is the proper response to 'path' and 'free_image' calls for a 
volume that no longer exists?
For path, should the call fail (e.g., 'die'), succeed with an empty 
string, or return a 'storage path'?


Tested on Proxmox VE 8.4.0

Best regards,
Andrei Perepiolkin




More information about the pve-devel mailing list