Bug 1254295 - Wrong cardinality of host.storage_domain_extensions, unbounded instead of 1
Summary: Wrong cardinality of host.storage_domain_extensions, unbounded instead of 1
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-api
Version: 3.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: m1
: 3.6.0
Assignee: Juan Hernández
QA Contact: Raz Tamir
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-17 16:07 UTC by Juan Hernández
Modified: 2016-03-10 06:13 UTC (History)
10 users (show)

Fixed In Version: 3.6.0-10
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-04 11:21:33 UTC
oVirt Team: Storage
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 44986 0 master MERGED restapi: Fix the cardinality storage connection extensions Never
oVirt gerrit 45024 0 ovirt-engine-3.6 MERGED restapi: Fix the cardinality storage connection extensions Never

Description Juan Hernández 2015-08-17 16:07:21 UTC
The XML schema definition of the host.storage_domain_extensions specifies "unbounded" for the "maxoccurs" attribute. This is wrong, and as a result the getter method of the Java class generated by the XJC compiler returns a list:

  List<StorageConnectionExtensions> getStorageConnectionExtensions() {
    ...
  }

This isn't an issue for the server, as this method isn't used at all. But it induces a compilation error in the Java SDK because the code generator assumes that this method returns only one element, and the code generated for the host decorator overrides it as follows:

  HostStorageConnectionExtensions getStorageConnectionExtensions() {
    ...
  }

The XML schema needs to be modified so that the value of maxoccurs is 1 instead of unbounded.

Comment 1 Raz Tamir 2015-08-23 11:37:09 UTC
Verified - rhevm-3.6.0-0.12.master.el6.noarch

Comment 2 Sandro Bonazzola 2015-11-04 11:21:33 UTC
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.


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