Description of problem: Currently when enable service-catlog and asb, there will create a broker, then user can provision the service, For service-catalog and template-service-broker we need also create a broker resource. Version-Release number of the following components: openshift v3.6.143 kubernetes v1.6.1+5115d708d7 etcd 3.2.1 openshift-ansible-3.6.140-1.git.0.4a02427.el7.noarch.rpm How reproducible: Always Steps to Reproduce: 1. After install get the broker [root@host-8-174-87 dma]# oc get broker NAME KIND ansible-service-broker Broker.v1alpha1.servicecatalog.k8s.io 2. 3. Actual results: 1. There is no broker about template-service-broker Expected results: 1. There should have a broker of template-service-broker Additional info:
openshift-ansible will enable this in the future, a documentation update or blog post will detail how to enable TSB for tech preview 3.6 environments.
Still no default tsb-broker if enable service-catalog and template-service-broker in openshift-ansible #oc get pods -n openshift-template-service-broker NAME READY STATUS RESTARTS AGE apiserver-qklhk 1/1 Running 0 1h [root@host-8-241-68 root]# oc get pods -n kube-service-catalog NAME READY STATUS RESTARTS AGE apiserver-s743w 1/1 Running 0 26m controller-manager-f8jlj 1/1 Running 0 26m [root@host-8-241-68 root]# oc get broker the server doesn't have a resource type "broker" openshift v3.7.0-0.133.0 kubernetes v1.7.0+80709908fd openshift-ansible-3.7.0-0.133.0.git.0.06c6bc7.el7.noarch.rpm
@ewolinet Default tsb-broker has be created after enable service catalog & tsb in openshift-ansible # oc get servicebroker NAME KIND template-service-broker ServiceBroker.v1alpha1.servicecatalog.k8s.io But still has no default serviceclass shown. openshift v3.7.0-0.144.2 kubernetes v1.7.6+a08f5eeb62
serviceclass should be auto generated by service-catalog controller-manager when there is a servicebroker, if it can't be created, there should be some bug for service-catalog. For this bug I think it can be verified.
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days