Bug 1582160

Summary: Unable to obtain a template list of a storage domain
Product: [oVirt] ovirt-engine Reporter: Dmitry Misharov <dmisharo>
Component: RestAPIAssignee: Tal Nisan <tnisan>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Leistnerova <lleistne>
Severity: medium Docs Contact:
Priority: unspecified    
Version: futureCC: bugs, lleistne, mshriver, tnisan, ylavi
Target Milestone: ovirt-4.2.4Flags: rule-engine: ovirt-4.2+
rule-engine: ovirt-4.3+
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-26 08:42:08 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:

Description Dmitry Misharov 2018-05-24 12:10:10 UTC
Description of problem:
This method http://ovirt.github.io/ovirt-engine-api-model/4.3/#services/storage_domain_templates/methods/list return nothing
returns:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<templates/>

Version-Release number of selected component (if applicable):
4.1.9.2-0.1.el7

How reproducible:
Always

Steps to Reproduce:
1. curl -k -u admin@internal:passsword https://rhv_host/ovirt-engine/api/storagedomains/some_id/templates 

Actual results:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<templates/>

Expected results:
List of templates should be returned.

Comment 1 Tal Nisan 2018-06-04 12:05:31 UTC
Managed to reproduce and looking through the code it seems like this actually never worked

Comment 2 Lucie Leistnerova 2018-06-11 11:24:50 UTC
List of templates on the storage domain returned

verified in ovirt-engine-restapi-4.2.4.2-0.1.el7_3.noarch

Comment 3 Sandro Bonazzola 2018-06-26 08:42:08 UTC
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.

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