Bug 1503091

Summary: Need to update apiservice from v1alpha1 to v1beta1 for servicecatalog.k8s.io
Product: OpenShift Container Platform Reporter: Weihua Meng <wmeng>
Component: Service BrokerAssignee: Jay Boyd <jaboyd>
Status: CLOSED ERRATA QA Contact: Weihua Meng <wmeng>
Severity: high Docs Contact:
Priority: high    
Version: 3.7.0CC: aos-bugs, chezhang, jmatthew, pmorie
Target Milestone: ---   
Target Release: 3.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-28 22:17:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Weihua Meng 2017-10-17 11:02:45 UTC 
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.
Comment 1 Paul Morie 2017-10-17 19:28:42 UTC 
https://github.com/openshift/origin/pull/16908 fixes this; will move to ON_QA when that merges
Comment 2 Jay Boyd 2017-10-18 13:32:30 UTC 
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.
Comment 4 Jay Boyd 2017-10-19 15:54:33 UTC 
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.
Comment 5 Weihua Meng 2017-10-20 01:28:17 UTC 
Got it.
Thanks.
Will check it when https://bugzilla.redhat.com/show_bug.cgi?id=1496694 verified.
Comment 6 Zhang Cheng 2017-10-29 16:18:14 UTC 
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.
Comment 9 errata-xmlrpc 2017-11-28 22:17:38 UTC 
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