Bug 1350343

Summary:	RESTAPI : Luns collection in ISCSI SD returns always with only one item
Product:	[oVirt] ovirt-engine	Reporter:	Fred Rolland <frolland>
Component:	RestAPI	Assignee:	Fred Rolland <frolland>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Raz Tamir <ratamir>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.0.0	CC:	amureini, bugs, tnisan
Target Milestone:	ovirt-4.0.1	Keywords:	Regression
Target Release:	4.0.1.1	Flags:	rule-engine: ovirt-4.0.z+ rule-engine: blocker+ rule-engine: planning_ack+ tnisan: devel_ack+ rule-engine: testing_ack+
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:	2016-07-19 06:25:22 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 Fred Rolland 2016-06-27 08:06:54 UTC

Description of problem:
When retrieving an ISCSI Storage Domain via REST API, the LUNs collection contains always only one LUN even if the SD contains more than one.

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


How reproducible:
100 %

Steps to Reproduce:
1. Create a ISCI storage domain with more than one LUN.
2. Get the storage domain via REST API (https://MY_ENGINE:8443/ovirt-engine/api/storagedomains)


Actual results:
The <logical_units> collection under <volume_group> contains only one LUN.

Expected results:
The <logical_units> collection under <volume_group> contains all the configured LUNs.

Additional info:

Comment 1 Red Hat Bugzilla Rules Engine 2016-06-27 10:07:32 UTC

This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 2 Raz Tamir 2016-07-03 16:21:48 UTC

Verified on rhevm-4.0.2-0.2.rc1.el7ev.noarch

Comment 3 Sandro Bonazzola 2016-07-19 06:25:22 UTC

Since the problem described in this bug report should be
resolved in oVirt 4.0.1 released on July 19th 2016, it has been closed with a
resolution of CURRENT RELEASE.

For information on the release, and how to update to this release, follow the link below.

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

http://www.ovirt.org/release/4.0.1/