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

Bug 1485951

Summary: NullPointerException when viewing the images in ovirt-image-repository storage domain
Product: [oVirt] ovirt-engine Reporter: shani <sleviim>
Component: BLL.StorageAssignee: shani <sleviim>
Status: CLOSED CURRENTRELEASE QA Contact: Raz Tamir <ratamir>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: amureini, bugs, tnisan
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 11:09:53 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
NullPointerException none

Description shani 2017-08-28 14:29:52 UTC
Created attachment 1319088 [details]
NullPointerException

Description of problem:
When viewing the images stored in ovirt-image-repository storage domain, after viewing the images stored in an empty openstack storage domain, a NullPointerException has been received on ovirt-engine's log. 

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

How reproducible:
100%

Steps to Reproduce:
1. Go to the images list on an empty openstack storage domain.
2. Go to the images list on ovirt-image-repository storage domain.
3. Watch the engine's log.

Actual results:
Exception: java.lang.NullPointerException

Expected results:
log error message: "Failed to retrieve image list"

Additional info:
-

Comment 1 Raz Tamir 2017-09-04 15:09:41 UTC
Verified on ovirt-engine-4.2.0-0.0.master.20170903205106.gitb17261a.el7.centos

No Exceptions when selecting Glance storage

Comment 2 Sandro Bonazzola 2017-12-20 11:09:53 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

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