Bug 755575

Summary:	RHEVM Backend: Classifying engine errors
Product:	[Retired] oVirt	Reporter:	Michael Pasternak <mpastern>
Component:	ovirt-engine-core	Assignee:	Barak <bazulay>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	acathrow, bazulay, iheim, jkt, lpeer, mpastern, Rhev-m-bugs, yeylon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	infra
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-08-08 07:12:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	755579

Description Michael Pasternak 2011-11-21 14:16:18 UTC

Description of problem:

i would like to suggest classifying engine errors (VdcBllMessages)
using these categories:

100-199. entity not found
200-300. missing parameters
300-399. no resources available
400-499. can't perform - user error
500-599. can't perform - server error
600-699. Unauthorized
700-x. Forbidden

this way rest api will be able mapping them to HTTP errors
e.g any error returned by engine CAN_DO_ACTION 100 < x < 200 will be converted
to HTTP 404 with CAN_DO_ACTION message detail

- this can be easily done by assigning id to each VdcBllMessages
enum member in range of one of mentioned categories.

Comment 1 Michael Pasternak 2012-10-18 07:52:29 UTC

*** Bug 722886 has been marked as a duplicate of this bug. ***

Comment 2 Barak 2013-08-04 10:46:07 UTC

Michael - Is this bug still relevant ?

Comment 3 Michael Pasternak 2013-08-08 07:12:04 UTC

(In reply to Barak from comment #2)
> Michael - Is this bug still relevant ?

already fixed.