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

Bug 1599054

Summary: Fix APIv3 deprecated/removed message
Product: [oVirt] ovirt-engine Reporter: Martin Perina <mperina>
Component: RestAPIAssignee: Martin Perina <mperina>
Status: CLOSED CURRENTRELEASE QA Contact: Radim Hrazdil <rhrazdil>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs, lsvaty
Target Milestone: ovirt-4.2.5Flags: rule-engine: ovirt-4.2+
Target Release: ---   
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: 2018-07-31 15:27:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.