Bug 1400996

Summary: Provide a mechanism to notify users that are using a deprecated version of the API
Product: [oVirt] ovirt-engine Reporter: Juan Hernández <juan.hernandez>
Component: RestAPIAssignee: Juan Hernández <juan.hernandez>
Status: CLOSED CURRENTRELEASE QA Contact: Radim Hrazdil <rhrazdil>
Severity: medium Docs Contact:
Priority: high    
Version: 4.0.6.2CC: bugs, juan.hernandez, lsvaty, mgoldboi, mperina, oourfali
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
mgoldboi: planning_ack+
juan.hernandez: devel_ack+
pstehlik: testing_ack+
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 11:20:30 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:

Description Juan Hernández 2016-12-02 14:14:24 UTC
Currently the server accepts version 3 and 4 of the API, even if version 3 is deprecated since version 4.0 of the engine. We need a mechanism to inform users that they are using a deprecated version of the API. This mechanism should, at least, send a message to the audit log.

Comment 3 Sandro Bonazzola 2017-01-25 07:54:55 UTC
4.0.6 has been the last oVirt 4.0 release, please re-target this bug.

Comment 4 Radim Hrazdil 2017-09-04 15:31:53 UTC
Verified that in 4.2.0-0.0.master.20170903205106.gitb17261a.el7.centos when using version 3 API, a message is logged in engine.log.

Comment 5 Sandro Bonazzola 2017-12-20 11:20:30 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

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