Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:
In 6.9, bug 1885846 and bug 1893512 marked RHEV APIv3 as deprecated. Then, bug 1927272 completely reported support for it. Support should never have been removed in 6.9 (it will be removed in 6.10) so bug 1927272 was reverted.
Creating this bug to make sure APIv3 indeed works again in 6.9.

Version-Release number of selected component (if applicable):
6.9

How reproducible:
Deterministic

Steps to Reproduce:
Try to use RHEV CR using API v3

Expected results:
It should be possible but a deprecation warning should be shown

Verified with Sat 6.9 snap 16.

Created an APIv3 CR in Satellite. Deprecation warning was shown and the CR was successfully created. On the RHEV, Apache forensic log shows that APIv3 is being used. After updating to APIv4 on the Satellite, APIv4 is used. After updating to APIv3, APIv3 is used. => Deprecation warning is shown but APIv3 can still be used.

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.9 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:1313