Bug 1849045

Summary: Differences between apidoc and REST API documentation about exporting VMs and templates to OVA
Product: Red Hat Enterprise Virtualization Manager Reporter: Juan Orti <jortialc>
Component: ovirt-engineAssignee: Arik <ahadas>
Status: CLOSED ERRATA QA Contact: Tamir <tamir>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.3.9CC: ahadas, dfodor, mavital, mkalinin
Target Milestone: ovirt-4.5.1Keywords: ZStream
Target Release: 4.5.1   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.5.1.2 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-14 12:54:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Juan Orti 2020-06-19 14:09:59 UTC
In RHV Manager you can browse the apidoc reference:

https://rhvm.example.com/ovirt-engine/apidoc/#/requests

To export VMs or templates to OVA, in the apidoc site there's the reference to the 'topathonhost' method, but in the official documentation that method is not listed. Instead the official documentation lists the 'export' method, so both references appear to not be synced.

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/rest_api_guide/services#services-template-methods-export

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/rest_api_guide/services#services-vm-methods-export

Also, Comparing the 'export' method for VMs and templates, it's not clear if the templates can be exported to OVA files indicating a host, directory and filename (it's possible).

Comment 1 Marina Kalinin 2022-04-19 18:58:49 UTC
Hi Arik,
Can you please take a look and see if RHV 4.4 documentation is correct or anything needs to be adjusted.
Thank you!

Comment 2 Arik 2022-04-20 15:59:13 UTC
(In reply to Juan Orti from comment #0)
> In RHV Manager you can browse the apidoc reference:
> 
> https://rhvm.example.com/ovirt-engine/apidoc/#/requests
> 
> To export VMs or templates to OVA, in the apidoc site there's the reference
> to the 'topathonhost' method, but in the official documentation that method
> is not listed. Instead the official documentation lists the 'export' method,
> so both references appear to not be synced.

This part seems to be fixed already, I don't see methods like 'topathonhost' in <engine-url>/ovirt-engine/apidoc/#/requests with the latest version of the engine anymore
 
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/
> html/rest_api_guide/services#services-template-methods-export
> 
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/
> html/rest_api_guide/services#services-vm-methods-export
> 
> Also, Comparing the 'export' method for VMs and templates, it's not clear if
> the templates can be exported to OVA files indicating a host, directory and
> filename (it's possible).

Yes, need to have a similar documentation for templates as well

Comment 7 Tamir 2022-06-19 10:40:58 UTC
The newly added documentation for templates are available in the link: https://{OVIRT-ENGINE-HOST}/ovirt-engine/apidoc/#services/template/methods/export
It looks good to me.

Verified on RHV 4.5.1-3.

Env:
    - Engine instance with RHV 4.5.1-3 (ovirt-engine-4.5.1.2-0.11.el8ev) and RHEL 8.6 installed.
    - 2 hosts with RHV 4.5.1-3 and RHEL 8.6 and with vdsm-4.50.1.3-1.el8ev.

Comment 11 errata-xmlrpc 2022-07-14 12:54:30 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: RHV Manager (ovirt-engine) [ovirt-4.5.1] security, bug fix and update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHSA-2022:5555

Comment 12 meital avital 2022-07-18 16:49:33 UTC
Due to QE capacity we are not going to cover this issue in our automation