Bug 1269256

Summary:	OpenShift REST API fieldSelector returning 400 BadRequest
Product:	OpenShift Container Platform	Reporter:	Øystein Bedin <obedin>
Component:	Master	Assignee:	Jordan Liggitt <jliggitt>
Status:	CLOSED CURRENTRELEASE	QA Contact:	weiwei jiang <wjiang>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.0.0	CC:	aos-bugs, jokerman, mmccomas, obedin, wsun
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-23 14:43:55 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:

Description Øystein Bedin 2015-10-06 19:47:06 UTC

Description of problem:


Version-Release number of selected component (if applicable):
OSE 3.0.x


How reproducible:
Use OSE v3.0.x REST API fieldSelector, e.g.:
GET https://master.ose.example.com:8443/oapi/v1/oauthaccesstokens?fieldSelector=userName%3Djoe


Steps to Reproduce:
1. Use REST API with the fieldSelector (for calls that supports it)
2. Observe that the response is 400 BadRequest

Actual results:
400 BadRequest


Expected results:
Response with data matching the fieldSelector query


Additional info:
E-mailed "openshift-sme" list and got response that this is a bug.

Comment 2 Øystein Bedin 2015-10-06 20:20:38 UTC

Just an extra piece of information, I've experienced this issue with both OSE v3.0.1 and v3.0.2.

Comment 3 Jordan Liggitt 2015-10-31 05:09:43 UTC

Fixed in https://github.com/openshift/origin/pull/5516

Comment 4 Jordan Liggitt 2015-11-02 14:20:13 UTC

Fixed in http://buildvm-devops.usersys.redhat.com/puddle/build/AtomicOpenShift/3.1/2015-11-01.2/

Comment 5 weiwei jiang 2015-11-03 05:57:30 UTC

Checked with 
# openshift version
openshift v3.0.2.905
kubernetes v1.2.0-alpha.1-1107-g4c8e6f4
etcd 2.1.2

And this issue has been fixed.