Changes between Version 5 and Version 6 of Ticket #17691, comment 1

Ticket #17691, comment 1

v5	v6
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-disk001 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 shows the status window displaying the original file name-disk001 and .VMDK extension (Windows 10-disk001.vmdk) despite the fact that a .VDI file with a new name was correctly generated as specified (Windows 10.vdi) in my session.
	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-disk001 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 shows the status window displaying the original (Windows 10.OVA) file name-disk001 and .VMDK extension (Windows 10-disk001.vmdk) despite the fact that a .VDI file with a new name was correctly generated as specified (Windows 10.vdi) in my session.