Description of problem: service-catalog apiserver failure shouldn't block console login Version-Release number of selected component (if applicable): openshift v3.7.0-alpha.1+7f10b2d-1126 How reproducible:Always Steps to Reproduce: 1.Setup env with service catalog enabled with service catalog apiservice issue, such as apiservice is still in old version "v1alpha1" $ oc get apiservice v1alpha1.servicecatalog.k8s.io -o yaml ... version: v1alpha1 .... 2.Login via OpenShift Web Console Actual results: 2.API_DISCOVERY returned and user could not login to web console Error Unable to load details about the server Expected results: 2.User should be able to login to web console for other operation even there is service-catalog apiservice error Additional info:
Image tested docker.io/openshift/origin latest 337320eb7425 5 hours ago 1.069 GB docker.io/openshift/origin-service-catalog latest a256e9de4aee 9 hours ago 316.6 MB
https://github.com/openshift/origin-web-common/pull/230
https://github.com/openshift/origin-web-console/pull/2274
Hi Sam, One question need to get response, we had been testing service catalog features/bugs with origin image, is this OK ? Do we need use ose images instead?
Are you blocked using the ansible installer to test service catalog? Ideally you would be testing with that. Running cluster up with origin images is better than not testing, but we should work to get you unblocked if you can't use the installer.
Currently we have some issues using ansible installer to create proper OCP envs(not serivce catalog issue) , so I have to verify on Origin. Checked this issue on v3.7.0-alpha.1+50389c0-1262 and it's been fixed. Move to VERIFIED