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

Bug 850819

Summary:	RFE Unify status' names in search field with api.xsd
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Gadi Ickowicz <gickowic>
Component:	ovirt-engine-restapi	Assignee:	Michael Pasternak <mpastern>
Status:	CLOSED WONTFIX	QA Contact:	Oded Ramraz <oramraz>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.1.0	CC:	acathrow, bazulay, dyasny, ecohen, iheim, jlibosva, mpastern, nlevinki, Rhev-m-bugs, ykaul
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	839551	Environment:
Last Closed:	2012-08-22 13:44:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	839551
Bug Blocks:

Description Gadi Ickowicz 2012-08-22 13:26:11 UTC

+++ This bug was initially created as a clone of Bug #839551 +++

Description of problem:
Nowadays object's statuses use no underscore in theirs names but REST-API uses the underscore in statuses.

e.g. search for all hosts that are non responsive is - status = nonresponsive
     in api the status is non_responsive

Version-Release number of selected component (if applicable):
ovirt-engine-backend-3.0.0_0001-1.6.fc16.x86_64

How reproducible:
Always

Steps to Reproduce:
1. In search field use 'Hosts: state =' and let the suggestion appear
2. Take a look at /api/capabilites on host's states
3. Compare non responsive representation for both approaches
  
Actual results:
Differs

Expected results:
Should be the same

Additional info:

Comment 1 Michael Pasternak 2012-08-22 13:44:49 UTC

by-design (enums in api are differs from UI), also this kind of change would break api

Comment 2 Jakub Libosvar 2012-08-22 14:05:51 UTC

The idea is changing enums in Backend for search engine, not the API. This bug should be opened agains Backend.