Environment
Filr 3
Filr 4
Filr 4
Situation
Import of OVF and VMDK files using VMware vSphere 6.7 Update 2 fails at last step with error:
Unhandled exception (1)Unfortunately, we hit an error that we weren't expected.The client may continue working, but at this point, we recommend refreshing your browser and submitting a bug report.Press the Esc key to hide this dialog and continue without refreshing.
Detailed message:
Cause: Possibly unhandled rejection: {}
Version: 1.33.3
Build: 12923304ESXi: 6.7.0
Browser: Mozilla/5.0
Exception stack:
updateSummaryPortlet@https://xxx.xxx.xxx.xxx/ui/scripts/main.js:375:273
@https://xxx.xxx.xxx.xxx/ui/scripts/main.js:375:5968
k/<@https://xxx.xxx.xxx.xxx/ui/scripts/main.js:324:23176
$digest@https://xxx.xxx.xxx.xxx/ui/scripts/main.js:324:28773
$evalAsync/<@https://xxx.xxx.xxx.xxx/ui/scripts/main.js:324:30501
e@https://xxx.xxx.xxx.xxx/ui/scripts/main.js:323:10069
tg/h.defer/c<@https://xxx.xxx.xxx.xxx/ui/scripts/main.js:323:11522 Resolution
The problem is expected to be fixed in upcoming update from VMware.
As a workaround for this problem, use one of the following methods.
1. Remove the small Filr.x86_64-4.0.0.155.mf file before beginnig. After unzipping the .ovf, you'll find three files, such as
Filr.x86_64-4.0.0.155-disk1.vmdk
Filr.x86_64-4.0.0.155.mf
Filr.x86_64-4.0.0.155.ovf
3 File(s) 1,914,193,751 bytes
Move the Filr.x86_64-4.0.0.155.mf to another location, then retry the depolyment.
2. Import the ovf using the ovftool command, as follows:
ovftool --datastore=${hypervisorDatastore} --network="VM Network" -dm=thin --skipManifestCheck --name=${VM_Name} $ovf vi://${hypervisorUserName}:${hypervisorPassword}\@${hypervisorIP}
For example:
ovftool --datastore=datastore1 --network="VM Network" -dm=thin --skipManifestCheck --name=Filr4-155 /tmp/Filr.x86_64-4.0.0.155.ovf vi://root:novell@123\@192.168.1.176
This assumes that the .ovf and .vmdk file are in the same directory.
3. Import the files using other hypervisor (for instance VMware Fusion) and migrate VM from there.