Hi,
I'm trying to upload a VM in an ovf+vmdk file format via the webservices SDK to a vcenter/esx and am running into some issues. Heres a brief description of what is being done:
In the vpx.log file on the esx's we get the following errors when we try to do this:
2009-07-03 15:22:17.751 0x16eb1b90 info 'HttpNfcServer' DiskUploadWorker PUT request /vmfs/volumes/4a23c7fd-05389109-b84c-0022192b1768/bob17/bob17.vmdk (/nfc/13794651-5df7-49ae-ab1f-e96dc543cdeb/disk-0.vmdk)
2009-07-03 15:22:17.752 0x16eb1b90 info 'HttpNfcServer' DiskUploadWorker File exists, overwrite not allowed: /vmfs/volumes/4a23c7fd-05389109-b84c-0022192b1768/bob17/bob17.vmdk
So obviously something in the import spec or ovf needs to convince ESX that WE actually want to overwrite these files, but i can't figure out what that is. If i pause my code right before the upload, delete all the vmdk files from the ESX, the PUT will succeed, and the VM upload will be successful.
Any tips or points would be appreciated - thanks!
Bob
I'm trying to upload a VM in an ovf+vmdk file format via the webservices SDK to a vcenter/esx and am running into some issues. Heres a brief description of what is being done:
- use the com.vmware.vim25.OvfCreateImportSpecParams method with a VM name, the ESX info, and network mappings
- the come.vmwarevim25.OvfCreateImportSpecResult that comes back looks ok (no warnings), except all the OvfFileItems have create = false (possibly a sign of something wrong right here)
- we then go on to create a HttpNfcLease via the importVApp command, and wait on it properly as per the api programming guide - i believe all this works fine
- when we iterate over the HttpNfcLeaseDeviceUrl.getUrls() and attempt to PUT the content to them, we get the 403's.
In the vpx.log file on the esx's we get the following errors when we try to do this:
So obviously something in the import spec or ovf needs to convince ESX that WE actually want to overwrite these files, but i can't figure out what that is. If i pause my code right before the upload, delete all the vmdk files from the ESX, the PUT will succeed, and the VM upload will be successful.
Any tips or points would be appreciated - thanks!
Bob