Bug 1499616

Summary:	Unable to find originating origin header
Product:	OpenShift Container Platform	Reporter:	Zhang Cheng <chezhang>
Component:	Service Broker	Assignee:	Matthew Staebler <mstaeble>
Status:	CLOSED ERRATA	QA Contact:	Zhang Cheng <chezhang>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.7.0	CC:	aos-bugs, jmatthew, mstaeble, pmorie, xtian
Target Milestone:	---
Target Release:	3.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-28 22:15:02 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:

Comment 1 Paul Morie 2017-10-13 16:13:57 UTC

A couple questions:

- How was this cluster created?  oc cluster up --service-catalog?
- Why is the original comment private?

John, I would like to reassign this to Matthew Staebler on my team, since it looks like the issue here is the catalog itself rather than a particular broker.  Any objections?

Comment 2 John Matthews 2017-10-16 10:22:44 UTC

Paul,

Reassigning to Matthew sounds good.

Comment 3 Matthew Staebler 2017-10-17 23:15:26 UTC

Using oc cluster up, this works already.
Using the ansible installer, this will work when https://github.com/openshift/openshift-ansible/pull/5746 is merged.

Zhang, how are you looking for the presence of the originating identity header?

Comment 4 Matthew Staebler 2017-10-17 23:17:59 UTC

This needs to be retested on the latest version.

Comment 6 Paul Morie 2017-10-18 14:29:17 UTC

Zhang-

I believe that Matthew's PR to openshift-ansible needs to merge before this will work for you.

Comment 8 Zhang Cheng 2017-10-27 15:40:05 UTC

I will verify this bug until BZ https://bugzilla.redhat.com/show_bug.cgi?id=1496426 is fixed.

Comment 12 errata-xmlrpc 2017-11-28 22:15:02 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/RHSA-2017:3188