Description of problem: the latest image does not support v1alpha1, leading to errors open this bug to track progress Version-Release number of selected component (if applicable): latest openshift3/ose-service-catalog:v3.7 v3.7.0-0.158.0.0 How reproducible: Always Steps to Reproduce: 1. install OCP cluster with service catalog enabled using image openshift3/ose-service-catalog:v3.7 2. check pods status when installation finished $ oc get pods -n kube-service-catalog $ oc logs controller-manager-gqgkz -n kube-service-catalog Actual results: $ oc get pods NAME READY STATUS RESTARTS AGE apiserver-qfwz8 1/1 Running 0 11h controller-manager-gqgkz 0/1 CrashLoopBackOff 143 11h $ oc logs controller-manager-gqgkz -n kube-service-catalog F1017 10:34:48.790238 1 controller_manager.go:198] error running controllers: failed to get supported resources from server: unable to retrieve the complete list of server APIs: servicecatalog.k8s.io/v1alpha1: the server could not find the requested resource Expected results: pods running, no errors Additional info: if update apiservice from v1alpha1 to v1beta1, pods will be running.
https://github.com/openshift/origin/pull/16908 fixes this; will move to ON_QA when that merges
Please ensure you are using a current build to pick up the alpha compatibility (see comment #1). If you are still experiencing issues, please provide more details on step 1 in the setup as I'm not experienced with using the mentioned images. Thanks.
I found out today that the Ansible installer is very out of date and missing key configuration items. That is about to be fixed by https://bugzilla.redhat.com/show_bug.cgi?id=1496694 I believe you are testing with the proper builds - most customers will be installing with Ansible. Please retry once 1486694 has been fixed.
Got it. Thanks. Will check it when https://bugzilla.redhat.com/show_bug.cgi?id=1496694 verified.
Verified with ose-ansible-service-broker:v3.7.0-0.185.0.0 and ose-service-catalog:v3.7.0-0.185.0.0 LGTM.
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