Bug 1871768 - Upload page does not state clearly which formats are supported
Summary: Upload page does not state clearly which formats are supported
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.0
Assignee: Gilad Lekner
QA Contact: Guohua Ouyang
Whiteboard: ux_issue
Depends On:
TreeView+ depends on / blocked
Reported: 2020-08-24 08:52 UTC by Tomas Jelinek
Modified: 2020-09-02 04:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)
the file to upload (171 bytes, application/gzip)
2020-08-24 08:52 UTC, Tomas Jelinek
no flags Details
proposed error text (42.14 KB, image/png)
2020-08-25 18:32 UTC, Matt
no flags Details

System ID Priority Status Summary Last Updated
Github openshift console pull 6487 None closed Bug 1871768: Add supported types to file upload 2020-09-11 01:51:04 UTC

Description Tomas Jelinek 2020-08-24 08:52:15 UTC
Created attachment 1712316 [details]
the file to upload

Description of problem:
Trying to upload the small attached tgz file (not a disk, just some files) fails with the following error: could not process image header

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. use the UI to upload the small tgz file attached to this bz
2. observe error

Actual results:
upload fails

Expected results:
upload passes

Additional info:

logs from the upload pod:

I0824 08:47:05.877045       1 uploadserver.go:63] Upload destination: /data/disk.img
I0824 08:47:05.877285       1 uploadserver.go:65] Running server on
I0824 08:47:11.731211       1 uploadserver.go:351] Content type header is ""
I0824 08:47:11.731384       1 data-processor.go:301] Calculating available size
I0824 08:47:11.731441       1 data-processor.go:313] Checking out file system volume size.
I0824 08:47:11.731455       1 data-processor.go:321] Request image size not empty.
I0824 08:47:11.731481       1 data-processor.go:326] Target size 1028173824.
E0824 08:47:11.731530       1 upload-datasource.go:41] Error creating readers: could not process image header: unexpected EOF
E0824 08:47:11.731612       1 data-processor.go:220] unexpected EOF
could not process image header
Unable to obtain information about data source
E0824 08:47:11.731663       1 uploadserver.go:363] Saving stream failed: Unable to obtain information about data source: could not process image header: unexpected EOF

Comment 1 Matt 2020-08-24 16:49:38 UTC
It seems like if this is the intention then we'd only want to surface the upload capability as a virtualization specific feature. That might impact how the UI should deliver this feature. Hopefully this is just a bug though :)

Comment 3 Matt 2020-08-24 17:05:04 UTC
I think we should clarify that there are file types that aren't supported. It may just be a link to the docs that says see here for supported formats.

Comment 4 Matt 2020-08-24 19:44:03 UTC
We should also provide an error that is more informative and point the user to the docs to better understand that supported types.

Comment 5 Tomas Jelinek 2020-08-25 05:45:30 UTC
In that case:
1: we need to name the button a bit differently. Something like: "New with OS Image Upload"
2: Probably the info msg on top should say something clarifying that this is only working for images and a link to docs to full metrics
3: Instead of the generic error we have today:
"Error Uploading Data
Request failed with status code 500"
Have an error saying also: "Please make sure you are uploading one of the supported formats" and a link to the doc.
@Matt: agree?

Moving this to UI than.

Comment 6 Matt 2020-08-25 18:31:09 UTC
Here's a revised design for this with this recent update

I agree with Tomas the alert for an upload that fails due to file format should be:

File upload failed

The format of the file you are uploading is not supported. Please use one of the supported formats.

Learn more about supported formats

Comment 7 Matt 2020-08-25 18:32:53 UTC
Created attachment 1712585 [details]
proposed error text

Here is what that error could look like

Comment 8 Matt 2020-08-25 18:34:20 UTC
It would be nice to not force the user out of the flow to see supported types. We could embed that table into the info alert at the top I just would be concerned that the supported types could change and the alert wouldn't be updated.

Comment 9 Gilad Lekner 2020-08-30 11:34:17 UTC
.img and .iso are supported aswell I assume? are they considered under the RAW category?

Comment 10 Gilad Lekner 2020-08-30 11:34:50 UTC
(In reply to Adam Litke from comment #2)
> tar.gz files are not supported.  Please see
> https://docs.openshift.com/container-platform/4.5/virt/virtual_machines/
> importing_vms/virt-importing-virtual-machine-images-datavolumes.html#virt-
> cdi-supported-operations-matrix_virt-importing-virtual-machine-images-
> datavolumes for more information about supported formats.

.img and .iso are supported aswell I assume? are they considered under the RAW category?

Comment 13 Guohua Ouyang 2020-09-02 04:09:56 UTC
After click browse and navigate local files, only .img .iso .qcow2 are showing for select, .tar are not showing to use.
Move bug to verified.

Note You need to log in before you can comment on or make changes to this bug.