Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1637831

Summary: Error provisioning ServiceInstance of ClusterServiceClass
Product: OpenShift Container Platform Reporter: Rutvik <rkshirsa>
Component: Service BrokerAssignee: jkim
Status: CLOSED DUPLICATE QA Contact: Zhang Cheng <chezhang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.9.0CC: aos-bugs, jkim, jmatthew, rkshirsa
Target Milestone: ---   
Target Release: 4.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-07 20:09:23 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 Rutvik 2018-10-10 07:49:18 UTC 
Description of problem:

We are hitting an issue similar to this Bug:
  [+] https://bugzilla.redhat.com/show_bug.cgi?id=1579194

When it is accessed from the console, it shows:
---
Error provisioning ServiceInstance of ClusterServiceClass xx at ClusterServiceBroker "template-service-broker": Status: 409; ErrorMessage: <nil>; Description: <nil>; ResponseError: <nil>
---

There is not an issue while creating the service instance from CLI.


# oc get pods -n kube-service-catalog 
NAME                          READY     STATUS    RESTARTS   AGE
po/apiserver-xx               1/1       Running   4          89d
po/controller-manager-xx      1/1       Running   1          4d


# oc get pods -n openshift-template-service-broker
NAME                 READY     STATUS    RESTARTS   AGE    
po/apiserver-xx      1/1       Running   4          89d
Comment 8 jkim 2018-11-07 20:09:23 UTC 
Hello,

This bug is a duplication of the following:
Provision failing with a 409 status error
https://bugzilla.redhat.com/show_bug.cgi?id=1579194

This is due to the fact that the broker was not handling multiple provision request properly. 

There are no workaround for this, however, this bug was fixed in v3.11

I will close this bug, but please feel free to re-open, if further discussion is required.

*** This bug has been marked as a duplicate of bug 1579194 ***