Cloning VM thru API doesn't return taskid

zpopovski

New Member
Feb 1, 2023
6
0
1
Hi,

I have a problem with cloning the vm because the /clone end point is not returning any taskid. I have implemented one workaround for testing if the VM is cloned or nor, so i am sending every 5 sec one get request on /config end point and i am testing if key "lock" exist and if the value is set to "clone" because i saw that key "lock" doesnt exist in the json response when the vm is cloned. To be honest, i dont like this workaround, can you please tell me possible reason why i am getting empty string instead of taskid when i am calling /clone api end point?
Thanks.
 
both the LXC and the Qemu clone endpoint return a UPID (if the task was successfully forked, if one of the preliminary checks failed it should return an error with corresponding status code). please provide the full request/response (censoring sensitive information).
 
both the LXC and the Qemu clone endpoint return a UPID (if the task was successfully forked, if one of the preliminary checks failed it should return an error with corresponding status code). please provide the full request/response (censoring sensitive information).
Thank alot for your confirmation for the endpoint UPID response, i found that the problem was in my code. Now i'll finally replace the workaround.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!