Created attachment 1293827 [details] catalog controller manager log Description of problem: After workaround BZ#1466727, continue testing. See the following details. Version-Release number of selected component (if applicable): openshift v3.6.131 How reproducible: Always Steps to Reproduce: 1. enable catalog service deployment in inventory host file 2. trigger installation 3. Actual results: installation failed at the following task: <--snip--> TASK [ansible_service_broker : Create the Broker resource in the catalog] ****** Monday 03 July 2017 09:59:16 +0000 (0:00:01.835) 0:34:45.273 *********** fatal: [openshift-120.lab.sjc.redhat.com]: FAILED! => { "changed": false, "failed": true } MSG: {u'returncode': 1, u'cmd': u'/usr/bin/oc create -f /tmp/brokerout-yIU50J -n default', u'results': {}, u'stderr': u'error: unable to recognize "/tmp/brokerout-yIU50J": no matches for servicecatalog.k8s.io/, Kind=Broker\n', u'stdout': u''} <--snip--> After the above failure, go to kube-service-catalog project, found controler manager pod is not running. # oc get po NAME READY STATUS RESTARTS AGE apiserver-bdsr2 1/1 Running 0 3m controller-manager-0nvqk 0/1 CrashLoopBackOff 3 3m Pls refer to attachment for pod log. Expected results: should be successful. Additional info: Try a lower version of openshift - v3.6.126.8, no such issue.
kubectl api-versions is not returning servicecatalog.k8s.io/v1alpha1 as expected, but I don't know why discovery is not finding that group. The problem doesn't appear to be with the certificates or with the discovery cache being stale.
We tried again in https://github.com/openshift/origin/pull/15022. I'm surprised it took this long to fail. These tests don't block merge?
Jeff to verify with latest commit, on success move to MODIFIED.
origin/master is working as expected
Verified this bug with openshift3/ose-service-catalog:latest (eb2a9b361302) and atomic-openshift-3.6.135-1.git.0.56fd7dc.el7.x86_64, installation is finished successfully, and controller-manager is running well. # oc get po NAME READY STATUS RESTARTS AGE apiserver-462z1 1/1 Running 0 5h controller-manager-hdpgj 1/1 Running 1 5h
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/RHEA-2017:1716