VMware import 404 error

[s3b]

@florent said in VMware import 404 error:

fix_dcpath

great job @florent , it works well now, just 2 things I don't run xo as root so I had errors on thick storage with vgchange rights so I used thin storage, and I had a problem with the TLS connection because I use a self-signed certificate for xo-server so I had to add in my systemd orchestra service:
Environment=NODE_TLS_REJECT_UNAUTHORIZED=0 and
then it worked very well.
One thing that confused me a bit is that there was no progress bar on the import page but it is clearly visible on the tasks page. Thank you again for the responsiveness and efficiency.

[florent]

@s3b the progress bar is on our roadmap , it will be even more needed when handling multiple import in parallel

[s3b]

@florent great !

[s3b]

@florent false joy , i have a problem now with another VM , this vm is on same place as baldr1-test , error :

message": "404 Not Found https://10.30.xx.xx/folder/undefined?dcPath=Webxxx&dsName=undefined",

th Vm is baldr2-test , the dsName should be the same but is undefined .

[florent]

@s3b dsName should be the datastore

what is the datastore name ? Are the vmx and vmdk files on the same one ? what is fileName of this disk in the vmx file ?

[s3b]

@florent the dsNAme is import-proxmox like for baldr1-test.
There is no .vmx so i think i have to delete from inventory the VM and recreate the vm and attach the disk . For now there is just 2 files :
[import-proxmox] baldr2-test/baldr2-test-import-ctk.vmdk
and
[import-proxmox] baldr2-test/baldr2-test-import.vmdk

.

[florent]

@s3b The vmx file is mandatory for the import, I didn't know that it was not for running on an esxi

Recreating it should solve the problem, I will improve our error handling on this case

[s3b]

@florent , delete vm from inventory , recreate the vm , move disk from old folder to new folder and then attach the disk to vm works fine

[florent]

@s3b I am more a XCP guy

[s3b]

@florent