Bug 1466031 - Ansible Service Broker does not work against pulp crane 2.13
Summary: Ansible Service Broker does not work against pulp crane 2.13
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.7.0
Assignee: Jason Montleon
QA Contact: DeShuai Ma
URL: https://github.com/openshift/ansible-...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-28 19:19 UTC by Jason Montleon
Modified: 2017-11-28 21:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-11-28 21:59:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 0 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-29 02:34:54 UTC

Description Jason Montleon 2017-06-28 19:19:28 UTC
Description of problem:
We're missing the 'Accept: application/json' header in our get request, which results in an internal server error 500 being spit out by crane instead of json:

<nil>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>500 Internal Server Error</title>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error and was unable to complete your request.  Either the server is overloaded or there is an error in the application.</p>

Version-Release number of selected component (if applicable):
ansible-service-broker-0.9.4-1.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Run RHCC Dev environment
2. Run catasb against it with the --rcm flag

Actual results:
Broker fails to bootstrap and displays ISE above

Expected results:
Broker should bootstrap

Additional info:

Comment 9 errata-xmlrpc 2017-11-28 21:59:33 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


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