Bug 1529607

Summary:	NPE when exporting disk with no description to OVA
Product:	[oVirt] ovirt-engine	Reporter:	Arik <ahadas>
Component:	BLL.Virt	Assignee:	Arik <ahadas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nisim Simsolo <nsimsolo>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	bugs, nsimsolo
Target Milestone:	ovirt-4.2.1	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Incorrect handling of disks with no description during the generation of an OVA. Consequence: VMs that include disks with no description could not be exported to OVA. Fix: The description of a disk is written to the OVF within an OVA only if it is set. Result: VMs that include disks with no description can be exported to OVA.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-12 11:53:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Arik 2017-12-28 23:14:50 UTC

Description of problem:
When we export a VM to an OVA file and the VM contains a disk with no description, the generation of the OVF fails with NPE.

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

How reproducible:
100%

Steps to Reproduce:
1. Export a VM with disk that has no description.

Actual results:
Export fails. CreateOvaCommand fails with NPE.

Expected results:
OVA should be created.

Comment 1 Nisim Simsolo 2018-01-07 13:35:49 UTC

Verification builds:
rhvm-4.2.1-0.2.el7
qemu-kvm-rhev-2.9.0-16.el7_4.13.x86_64
vdsm-4.20.11-1.el7ev.x86_64
sanlock-3.5.0-1.el7.x86_64
libvirt-client-3.2.0-14.el7_4.7.x86_64

Verification scenario:
Export VM with no disk description to an OVA
Verify VM exported successfully.

Comment 2 Sandro Bonazzola 2018-02-12 11:53:58 UTC

This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.1 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.