Bug 1400996 - Provide a mechanism to notify users that are using a deprecated version of the API
Summary: Provide a mechanism to notify users that are using a deprecated version of th...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: 4.0.6.2
Hardware: Unspecified
OS: Unspecified
high
medium vote
Target Milestone: ovirt-4.2.0
: 4.2.0
Assignee: Juan Hernández
QA Contact: Radim Hrazdil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-02 14:14 UTC by Juan Hernández
Modified: 2017-12-20 11:20 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:20:30 UTC
oVirt Team: Infra
rule-engine: ovirt-4.2+
mgoldboi: planning_ack+
juan.hernandez: devel_ack+
pstehlik: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 67745 0 master MERGED restapi: Create audit message for deprecated API usage 2017-02-13 12:05:44 UTC

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.


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