Bug 1466031 - Ansible Service Broker does not work against pulp crane 2.13
Ansible Service Broker does not work against pulp crane 2.13
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker (Show other bugs)
3.6.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 3.7.0
Assigned To: Jason Montleon
DeShuai Ma
https://github.com/openshift/ansible-...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-28 15:19 EDT by Jason Montleon
Modified: 2017-11-28 16:59 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-11-28 16:59:33 EST
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 Jason Montleon 2017-06-28 15:19:28 EDT
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 16:59:33 EST
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.