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:
Starting RHV 4.2, the v3 of the RHV API will no longer exist.
Please move all requests to work with v4.
v4 is supported since RHV 4.0, so for the basic requests you're using, it will work with RHV 4.0 and above.
Depending on the release schedule of Satellite, and the required support matrix, consider keeping both the v3 and v4 code.
(In reply to Itamar Heim from comment #1)
> what do you mean by "move"?
> wouldn't this break satellite 6 compatibility for rhev 3 ?
> i can understand "add"?
That's exactly what I meant when I wrote :
" Depending on the release schedule of Satellite, and the required support matrix, consider keeping both the v3 and v4 code."
Because I don't know when is the next satellite release, and what RHV versions it should support.
Bryan, this is not a dup. Bug 1405489 merely changed the end point from /api to /ovirt-engine/api or so, so it'll still work with RHV 4.0 using the v3 API.
This specific bug is a request to move to v4 API altogether.
To avoid disruption and risks I'd suggest to add to Satellite a new provider for oVirt 4 (not sure if "provider" is the right term in the Satellite architecture), while preserving the existing oVirt 3 provider.
Both should available in the GUI, temporarely, till we completely drop support for version 3 of the API. The user should be ableo choose which one to use. We should also provide a documented procedure to manually switch from the old one to the new one.
If I understand correctly the current support for RHV is based in the 'ovirt' provider of the 'fog' gem. If that is correct then I'd suggest the same approach there: add a new 'ovirt4' provider to 'fog', while preserving the existing 'ovirt' one. That new 'ovirt4' provider should use the 'ovirt-engine-sdk' gem instead of 'rbovirt'.
The feature has been merged into the foreman: it's currently marked as experimental, and users still can use the v3 (which is set by default), until we get confirmation from QE that the v4 can fully replace v3,
we are tracking the v4-related issues in http://projects.theforeman.org/issues/19568.
Regardless, it's possible now to start using the API v4 in current upstream, and I'm marking this PZ as POST
(In reply to Ivan Necas from comment #12)
> The feature has been merged into the foreman: it's currently marked as
> experimental, and users still can use the v3 (which is set by default),
> until we get confirmation from QE that the v4 can fully replace v3,
When will this happen?
>
> we are tracking the v4-related issues in
> http://projects.theforeman.org/issues/19568.
>
> Regardless, it's possible now to start using the API v4 in current upstream,
> and I'm marking this PZ as POST
This change would likely make it into 6.4, pending testing.
Comment 16Lukáš Hellebrandt
2018-08-28 12:41:17 UTC
Verified with Sat 6.4 snap 18.
The CR edit page now contains a checkbox for API version selection. Version 4 is marked as experimental.
While there are some bugs (BZs reported), it is now generally possible to do the same using API v3 and v4.
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, 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-2018:2927