Bug 1534467

Summary:	Can not get expected response while using invalid bearer token
Product:	OpenShift Container Platform	Reporter:	Zihan Tang <zitang>
Component:	Service Broker	Assignee:	Shawn Hurley <shurley>
Status:	CLOSED ERRATA	QA Contact:	Zihan Tang <zitang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.9.0	CC:	aos-bugs, chezhang, jmatthew
Target Milestone:	---
Target Release:	3.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-28 14:19:05 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 Zihan Tang 2018-01-15 10:21:38 UTC

openshift v3.9.0-0.19.0
kubernetes v1.9.0-beta1
ASB : 1.1.4

Description of problem:
Run curl command in client  with an invalid bearer tokern ,  the response is not readable  .
In v3.7 , the response is 'Unauthorized' 
in v3.9 the response is 'no kind is registered for the type v1.Status'

How reproducible:
always

Steps to Reproduce:
1. Get the asb route
2. Run command in client
curl -H Authorization: Bearer XXXXXXXXXXXX -sk https://asb-1338-openshift-ansible-service-broker.apps.0115-fre.qe.rhcloud.com/ansible-service-broker/v2/catalog

Actual results:
Curl response is 
     no kind is registered for the type v1.Status

Comment 1 Shawn Hurley 2018-01-18 15:26:33 UTC

Updated with PR: https://github.com/openshift/ansible-service-broker/pull/647

With return a v1.Status object from kubernetes now. Example:
{"kind": "Status",
 "apiVersion": "v1",
 "metadata": {},
 "status": "Failure",
 "message": "Unauthorized",
 "reason": "Unauthorized",
 "code": 401
}

Comment 8 errata-xmlrpc 2018-03-28 14:19:05 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0489