Service catalog fails because Template Service Broker won't start
Issue
- The service catalog deploy fails when deploying the template service broker. It creates the service apiserver.openshift-template-service-broker.svc, but it cannot connect to it.
- We checked the daemonset and there are no pods running:
$ oc project openshift-template-service-broker
Now using project "openshift-template-service-broker" on server "https://openshift.internal.cyrax2.example.com:443".
$ oc get all
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
ds/apiserver 0 0 0 0 0 region=infra 1d
- Upgrade fails because tsb will not start
TASK [template_service_broker : Verify that TSB is running] ********************************************************************
. . .
FAILED - RETRYING: Verify that TSB is running (1 retries left).
fatal: [test.example.com]: FAILED! => {"attempts": 60, "changed": false, "content": "", "failed": true, "msg": "Status code was not [200]: Request failed: <urlopen error [Errno 111] Connection refused>", "redirected": false, "status": -1, "url": "https://apiserver.openshift-template-service-broker.svc/healthz"}
. . .
Failure summary:
1. Hosts: test.example.com
Play: Upgrade Service Catalog
Task: Verify that TSB is running
Message: Status code was not [200]: Request failed: <urlopen error [Errno 111] Connection refused>
Environment
- Red Hat OpenShift Container Platform
- 3.7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.