Uploading gzip files with no tar in vcenter DS should fail gracefully
|Assignee:||MIGUEL ANGEL ALVAREZ CABRERIZO||% Done:|
|Target version:||Release 5.2|
Or be supported
#3 Updated by Miguel Ángel Álvarez Cabrerizo over 4 years ago
- Due date set to 10/03/2016
- Status changed from New to Closed
- Start date changed from 07/26/2016 to 09/30/2016
Tested on master branch.
- Registering plain VMDK standalone file. Working.
- Registering VMDK standalone file zipped with GZIP. Working.
- Registering VMDK standalone file tar and gzipped. Working.
- Registering VMDK flat and descriptor files inside a tar gzipped file. Working.
Apparently all works out of the box in master branch.
#7 Updated by Miguel Ángel Álvarez Cabrerizo over 4 years ago
- Due date deleted (
- % Done changed from 100 to 10
Further testing shows the following behavior:
- Standalone VMDK files have no extension when uploaded to vCenter datastores. Extension is part of the name e.g smalltest*vmdk*
- GZipped standalone VMDK files has a hash as the name loosing original name and extension. e.g 3b595250c99fcf23a796bf0bcdcaad73. That hash is the same hash used as a name for the folder created in the datastore.
- Standalone and flat files inside a tar.gz works fine, original name and extension are preserved.
#8 Updated by Miguel Ángel Álvarez Cabrerizo over 4 years ago
- % Done changed from 10 to 100
PR solves the following issues:
- Uploading standalone vmdk file (uncompressed) looses vmdk file extension so vCenter can't browse it. Now a vmdk extension is added.
- Uploading standalone vmdk file compressed with GZIP or BZIP2 changes file name to folder hash. Now a human readable name based on the original name and extension is added so it can be browsed.
- Upload flat VMDk files in a tar.gz. OK
- Upload flat VMDk files in a tar.bz2. OK
- Upload flat VMDk files in a tar. OK
- Upload standalone VMDK file. OK
- Upload standalone VMDK file gzipped. OK
- Upload standalone VMDK file bzipped. OK
- Upload standalone VMDK file in a tar.gz. OK