Changes between Version 1 and Version 2 of Ticket #17691, comment 1
- Timestamp:
- Apr 17, 2018 9:12:46 AM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #17691, comment 1
v1 v2 1 When importing a .OVA appliance and specifying a new file name manually (in the Virtual Disk Image column), the file name in the status window shows as the default name and extension (.OVA filename and .VMDK extension) instead of the new name and extension (.VDI for example). The appliance correctly imports with the new file name and extension (.VDI file in my case) so the bug is just the status window (file name & extension for the import). The attached screenshot shows the original file nameand .VMDK extension despite the fact that a .VDI file with a new name was correctly generated as specified.1 When importing a .OVA appliance and specifying a new file name manually (in the Virtual Disk Image column), the file name in the status window shows as the default name and extension (.OVA filename-disk001 and .VMDK extension) instead of the new name and extension (.VDI for example). The appliance correctly imports with the new file name and extension (.VDI file in my case) so the bug is just the status window (file name & extension for the import). The attached screenshot show the status window displaying the original file name-disk001 and .VMDK extension despite the fact that a .VDI file with a new name was correctly generated as specified.

