Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1927272 - Remove API v3 from fog-ovirt
Summary: Remove API v3 from fog-ovirt
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - RHEV
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.10.0
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-10 12:42 UTC by Shira Maximov
Modified: 2021-11-16 14:10 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-16 14:10:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 30793 0 Normal Closed Remove API v3 from fog-ovirt 2021-02-18 09:37:24 UTC
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:10:12 UTC

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


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