Unable to provision services using Openshift Template Service Broker in OCP 3

Solution Unverified - Updated -

Issue

  • OpenShift Template Service Broker appeared to become unresponsive after around ~2 months of uptime. Users experiencing the errors similar to the following when trying to provision/deprovision services from the catalog:
Error deprovisioning, ClusterServiceClass (K8S:
        "73182d1c-919f-11e8-8b14-005056b1842f" ExternalName: "redis-persistent")
        at ClusterServiceBroker "template-service-broker": Delete
        https://apiserver.openshift-template-service-broker.svc:443/brokers/template.openshift.io/v2/service_instances/fe7fca5f-6e28-464b-8860-c83b26b981e9?accepts_incomplete=true&plan_id=73182d1c-919f-11e8-8b14-005056b1842f&service_id=73182d1c-919f-11e8-8b14-005056b1842f:
        dial tcp <IP ADDR>:443: connect: cannot assign requested address
  • When trying to deploy JBoss EAP 7.0 (no https) service, getting the following error:
The provision call failed and will be retried: Error communicating with broker for provisioning: Put https://apiserver.openshift-template-service-broker.svc:443/brokers/template.openshift.io/v2/service_instances/1ac5265d-7332-4291-ae0d-c82f30a3d4eb?accepts_incomplete=true: dial tcp: lookup apiserver.openshift-template-service-broker.svc: device or resource busy.

Environment

Red Hat OpenShift Container Platform 3.9

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content