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

Bug 1601227

Summary:	image upload - command failure on resume
Product:	[oVirt] ovirt-engine	Reporter:	Daniel Erez <derez>
Component:	BLL.Storage	Assignee:	Daniel Erez <derez>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Yosi Ben Shimon <ybenshim>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2.5	CC:	bugs, tnisan
Target Milestone:	ovirt-4.2.5	Flags:	rule-engine: ovirt-4.2+ rule-engine: blocker+
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:27:21 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:

Description Daniel Erez 2018-07-15 11:03:59 UTC

Description of problem:
When resuming an image upload from the WebAdmin, a command failure is thrown
(NPE for silent resume, CCE for manual resume).

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

How reproducible:
100%

Steps to Reproduce:
1. Start an image upload from the WebAdmin.
2. Pause.
3. Resume.

Actual results:
Command failure.

Expected results:
Upload resumes.

Comment 1 Yosi Ben Shimon 2018-07-25 12:16:11 UTC

Tested using:
ovirt-engine-4.2.5.2-0.1.el7ev.noarch

Uploaded image:
# qemu-img info new_img.qcow2
image: new_img.qcow2
file format: qcow2
virtual size: 10G (10737418240 bytes)
disk size: 1.5G
cluster_size: 65536
Format specific information:
    compat: 0.10
    refcount bits: 16

The image uploaded successfully after a pause and resume and no exception was thrown.

Moving to VERIFIED

Comment 2 Sandro Bonazzola 2018-07-31 15:27:21 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.