-
Notifications
You must be signed in to change notification settings - Fork 910
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
govc import ova template failing with version v0.38.0 #3483
Comments
Howdy 🖐 abhinandanbaheti ! Thank you for your interest in this project. We value your feedback and will respond soon. If you want to contribute to this project, please make yourself familiar with the |
Not aware of any related issues. Can you add the
|
Error trace (IP is masked) |
That's only a tiny snippet. Did you create 2 log files as requested, one with each govc version? You can then attach the files (paper clip icon), rather than paste. |
thanks, I have DM'ed you the trace log and ova details in the VMware gChat Space, please let me know, if you find any issue. |
FWIW, this is also happening here with govc 0.39.0 and vSphere 8.0.1 while import talos as described in the |
I also have the same problem with 0.39.0 and 0.38.0 and vSphere 8.0.3. |
Haven't heard from @abhinandanbaheti in a couple weeks, I did not get trace logs or ova to reproduce with. |
I see the problem, it's caused by "DiskProvisioning": "monolithicSparse", I'll put a fix together tomorrow, along with tests to make sure we don't hit this again. In the meantime, you can change to the previous default or just remove the option from the json spec: "DiskProvisioning": "flat" |
PR vmware#3427 changed to using generated enum lists in various govc commands. This also changed the default DiskProvisioning value from "flat" to "monolithicSparse", which results in a DeviceUnsupportedForVmPlatform fault when importing. This change restores the default to "flat". The default values for IPProtocol and IPAllocationPolicy had not changed, but this commit explicitly sets their values rather than using first element of the generated list. Fixes vmware#3483
Following command to upload vmtemplate fails with the latest released version of govc - v0.38.0, while it works with previous version and it successfully uploads the vm template to vCenter.
govc import.ova -ds=${DATA_STORE} -host=${ESXI_HOST} -options=${TEMPLATE}.json ${TEMPLATE}.ova
Following error observed
govc: The device or operation specified at index '1' is not supported for the existing virtual machine platform.
Could it be related to any configuration issue or incompatibility with the VM template and the vCenter ?
The text was updated successfully, but these errors were encountered: