Bug 1599054 - Fix APIv3 deprecated/removed message
Summary: Fix APIv3 deprecated/removed message
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.5
: ---
Assignee: Martin Perina
QA Contact: Radim Hrazdil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-08 11:13 UTC by Martin Perina
Modified: 2018-07-31 15:27 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-07-31 15:27:58 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 92886 0 master MERGED restapi: Fix APIv3 deprecated/removed message 2020-07-07 19:56:35 UTC
oVirt gerrit 92907 0 ovirt-engine-4.2 MERGED restapi: Fix APIv3 deprecated/removed message 2020-07-07 19:56:35 UTC

Description Martin Perina 2018-07-08 11:13:24 UTC
Description of problem:

We are emitting this audit log error when client accesses engine using APIv3:

​"""
Client from address "10.4.4.68" ​​is using version 3 of the API, ​​which has been deprecated since version 4.0 of the engine, and will no longer be supported starting with version 4.3. Make sure to update that client to use a supported versions of the API and the SDKs, before upgrading to version 4.3 of the engine.
"""

But we already know that APIv3 will not be removed in 4.3, so updating to 4.4

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Radim Hrazdil 2018-07-13 11:09:23 UTC
Verified that the deprecation message states:
... will no longer be supported starting with version 4.4. Make sure...

Software Version:4.2.5.1-0.1.el7ev

Comment 2 Sandro Bonazzola 2018-07-31 15:27:58 UTC
This bugzilla is included in oVirt 4.2.5 release, published on July 30th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.5 release, it has been closed with a resolution of CURRENT RELEASE.

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


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