Bug 850819 - RFE Unify status' names in search field with api.xsd
RFE Unify status' names in search field with api.xsd
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-restapi (Show other bugs)
3.1.0
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Michael Pasternak
Oded Ramraz
:
Depends On: 839551
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-22 09:26 EDT by Gadi Ickowicz
Modified: 2014-08-21 21:41 EDT (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 839551
Environment:
Last Closed: 2012-08-22 09:44:49 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Gadi Ickowicz 2012-08-22 09:26:11 EDT
+++ 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 09:44:49 EDT
by-design (enums in api are differs from UI), also this kind of change would break api
Comment 2 Jakub Libosvar 2012-08-22 10:05:51 EDT
The idea is changing enums in Backend for search engine, not the API. This bug should be opened agains Backend.

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