Improvements to Proxmox 4.2

Hello everyone , I will be posting two improvements to the Proxmox developers.
First : When you canceled a backup running a VM status VM is as " locked " being necessary to enter via shell and run the command qm unlock VM_ID .
Second : During restore a VM for the proxmoxo interface ID allows me to create a new VM with the same VM ID to restore underway causing failure VM restore.
:);)
 
I can at least verify that the "vm stays locked after problems with a backup" also happends to me several times. This mostly happens when the target storage has some kind of trouble (disk full, network connection lost). But I didn't notices this the last few weeks so maybe the bug is "gone" due to some other work.
 
I can at least verify that the "vm stays locked after problems with a backup"
Yes this is the accepted behavior.
But antoniormjr wrote
When you canceled a backup running
So user cancellation will not lock the VM. A backup failure will lock the VM so the admin will check why it is locked

Second : During restore a VM for the proxmoxo interface ID allows me to create a new VM with the same VM ID to restore underway causing failure VM restore
It is not possible to create a VM with the same VMID, but it is true the wizard shows the VMID is free.

May be your are on an old version?
 
I know it's not possible to create a VM with the same ID, however I realized the next test.

- My Proxmox is not with any VM installed.
- Initiate the restore of the VM ID 100
- During the restore process (10%)
- I created a new VM with ID 100
- After the end of the restore fails because there is already a VM ID 100.

In summary the Proxmox could not let me create a VM ID 100 as already used the ID 100 in the restore.

I know Proxmox creates the conf file and the vm ID at the end of the restore, I believe the Proxmox have to first create the conf file and the ID and continue after the disk creation.