Bug 1510764 - Input validation - no signature found should throw ValidationException
Summary: Input validation - no signature found should throw ValidationException
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
medium
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: 2017-11-08 07:42 UTC by Ori Liel
Modified: 2017-12-20 11:23 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:23:26 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 84187 0 master MERGED No Signature Found Should Throw ValidationException 2017-11-15 14:56:41 UTC
oVirt gerrit 84538 0 master MERGED restapi: Update to model 4.2.26 and model 1.2.15 2017-11-23 14:28:15 UTC

Description Ori Liel 2017-11-08 07:42:38 UTC 
Description of problem:

Currently auto-generated code from live-documentation, which selects the correct signature of a method to be invoked, throws an IllegalArgumentException if no matching signature is found. 


How reproducible:

1. Make an API request which invokes signature-detection
2. Provide arguments which don't match any possible signature


Actual results:

A non-graceful failure containing a stack-trace of the exception.

Expected results:

A response object containing the error message. 

Additional info:
Comment 1 Radim Hrazdil 2017-12-19 14:04:37 UTC 
Verified that ValidationException is thrown instead of IllegalArgumentException.
Version 4.2.0.2
Comment 2 Sandro Bonazzola 2017-12-20 11:23:26 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.