Reported upstream: https://github.com/openshift/ansible-service-broker/issues/701 Description of problem: I made the following request to a broker that was configured to launch APB on bind and to auto-escalate: 172.17.0.1 - - [29/Jan/2018:13:58:01 +0000] "DELETE /ansible-service-broker/v2/service_instances/ad7e24ee-4344-4a72-8e2a-4bbfe0399c13/service_bindings/133a20b9-c045-4458-90b3-b759e222fb99?plan_id=7f4a5e35e4af2beb70076e72fab0b7ff&servuce_id=1dda1477cace09730bd8ed7a6505607e&accepts_incomplete=true HTTP/1.1" 200 58 You can see that it returned a 200 response code instead of 202. The rest of the response looks correct per the spec: HTTP/1.1 200 OK Content-Type: application/json Date: Mon, 29 Jan 2018 13:58:01 GMT Content-Length: 58 Set-Cookie: d05351dd24520dce41f310fcfc112523=40019baab3f211b0fa625c5f1e06dba2; path=/; HttpOnly; Secure Cache-control: private { "operation": "4e62e770-715a-42d5-b3e7-87df6dd6ae25" } Version-Release number of selected component (if applicable): 1.1 How reproducible: always Steps to Reproduce: 1. configure the broker to run APBs on bind/unbind and auto-escalate 2. DELETE a binding via the OSB API and specify query parameter "accepts_incomplete=true" Actual results: 200 response code Expected results: 202 response code
https://github.com/openshift/ansible-service-broker/pull/702
PR #702 was merged in 1.1.9, Changing status to ON_QA since asb downstream image ready for test.
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-2018:2013