Bug 987986 - [oVirt] [glance] NPE on disk export
Summary: [oVirt] [glance] NPE on disk export
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.3
Assignee: Ayal Baron
QA Contact:
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-24 13:53 UTC by Mike Kolesnik
Modified: 2016-02-10 16:39 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-23 07:35:27 UTC
oVirt Team: Storage
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 17342 0 None None None Never

Description Mike Kolesnik 2013-07-24 13:53:41 UTC
Description of problem:
Got NPE on export of disk to a glance storage domain


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


How reproducible:
Always


Steps to Reproduce:
1. Create a glance domain by creating a glance provider
2. Create a disk
3. try to export the disk to the glance domain
  
Actual results:
http://pastebin.test.redhat.com/154848


Expected results:
Should succeed


Additional info:
Tried with both preallocated/thin provisioned disks.
Disks had no snapshots.

Comment 1 Federico Simoncelli 2013-07-24 15:31:32 UTC
I've been able to reproduce this on master as well.
UI model is capable to set the correct parameters for the export, in particular the destinationStorageDomain uuid.

When the parameters are then received by the backend the destinationStorageDomain uuid is null.

I have the feeling that this has to do with serialization.
I'm going to look into this because it's mandatory to be fixed.

Comment 2 Federico Simoncelli 2013-07-26 15:42:26 UTC
As I believed this is a serialization issue. The workaround is to add an (apparently unused) default constructor for the export parameters.

Comment 3 Itamar Heim 2013-08-21 16:42:30 UTC
as RC is built, moving to ON_QA (hopefully did not catch incorrect bugs when doing this)

Comment 4 Itamar Heim 2013-09-23 07:35:27 UTC
closing as this should be in 3.3 (doing so in bulk, so may be incorrect)


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