Bug 1927272

Summary: Remove API v3 from fog-ovirt
Product: Red Hat Satellite Reporter: Shira Maximov <mshira>
Component: Compute Resources - RHEVAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.8.0CC: bbuckingham, lzap, orabin, zhunting
Target Milestone: 6.10.0Keywords: Triaged
Target Release: Unused   
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: 2021-11-16 14:10:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Shira Maximov 2021-02-10 12:42:19 UTC

Comment 1 Shira Maximov 2021-02-10 12:42:25 UTC
Created from redmine issue https://projects.theforeman.org/issues/30793

Comment 2 Shira Maximov 2021-02-10 12:42:28 UTC
Upstream bug assigned to mshira

Comment 3 Bryan Kearney 2021-02-10 16:02:27 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30793 has been resolved.

Comment 9 Lukáš Hellebrandt 2021-02-25 11:06:59 UTC
There is bug 1885846 and bug 1893512 fixed in Sat 6.9 to mark APIv3 as deprecated. Suddenly removing it completely doesn't seem like something we want to do in this release. Description of PR for this BZ:

Remove the option to choose V3 API
Remove deprecations warnings
Any old CR with API v3 will work with v4

Shira, I think this BZ is inconsistent with the two mentioned.

Comment 10 Lukáš Hellebrandt 2021-02-25 11:10:46 UTC
I see Shira manually set this to 6.10 and probably some bot set it back to 6.9, can someone fix this? Brad?

Comment 11 Shira Maximov 2021-02-25 11:48:11 UTC
Thanks Lukas, I've changed the flags now, I think now it shouldn't be changed again

Comment 17 Lukáš Hellebrandt 2021-07-12 19:02:52 UTC
Verified with Sat 6.10.0 snap 5.0 and Sat 6.9.3 snap 2.0.

It's not possible to set APIv3 through WebUI, the checkbox isn't there.
It's not possible to set APIv3 through Hammer: `Error: Unrecognised option '--use-v4'`
It's not possible to set APIv3 through API: `Backtrace for 'Action failed' error (ActiveModel::UnknownAttributeError): unknown attribute 'use_v4' for Foreman::Model::Ovirt.`

After adding an APIv3 RHEV CR into Sat 6.9.3 and upgrading it (bypassing unrelated bugs), the RHEV CR still works, including VM operations in Satellite, and uses APIv4:

rhev-host.domain $ grep -o Version:[0-9] /var/log/httpd/forensic_log
Version:4
Version:4
[...]

Comment 20 errata-xmlrpc 2021-11-16 14:10:01 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: Satellite 6.10 Release), 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-2021:4702