Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1594775

Summary: download raw image - wrong total value in progress
Product: [oVirt] ovirt-engine Reporter: Daniel Erez <derez>
Component: Backend.CoreAssignee: Daniel Erez <derez>
Status: CLOSED CURRENTRELEASE QA Contact: Natalie Gavrielov <ngavrilo>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.4CC: bugs, nsoffer
Target Milestone: ovirt-4.2.5Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-31 15:28:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
download raw image none

Description Daniel Erez 2018-06-25 12:12:24 UTC
Created attachment 1454336 [details]
download raw image

Description of problem:
When downloading a disk, created from an uploaded raw image, the total value in progress is the actual size instead of virtual size. Note: since we upload the disk into a sparse image, we must download the entire file (virtual size), as we don't know the bytes allocation (data/zeros) in the disk.

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

How reproducible:
100%

Steps to Reproduce:
1. Upload a raw image (e.g. 100MB).
2. Download the created disk.

Actual results:
The total value in progress is 100MB

Expected results:
The total value in progress should be 1024MB

Additional info:
See attached screenshot.

Comment 1 Natalie Gavrielov 2018-07-25 12:43:09 UTC
Verified using 4.2.5.2_SNAPSHOT-76.g2d45cde.0.scratch.master.el7ev.

Comment 2 Sandro Bonazzola 2018-07-31 15:28:25 UTC
This bugzilla is included in oVirt 4.2.5 release, published on July 30th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.5 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.