Bug 1502574

Summary: service-catalog apiservice failure shouldn't block console login
Product: OKD Reporter: Yadan Pei <yapei>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED CURRENTRELEASE QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.xCC: aos-bugs, mmccomas, spadgett, wmeng, yapei
Target Milestone: ---   
Target Release: 3.x   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-23 10:12:30 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 Yadan Pei 2017-10-16 09:21:01 UTC
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:

Comment 1 Yadan Pei 2017-10-16 09:26:23 UTC
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

Comment 4 Yadan Pei 2017-10-19 07:45:41 UTC
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?

Comment 5 Samuel Padgett 2017-10-19 11:58:35 UTC
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.

Comment 6 Yadan Pei 2017-10-23 07:18:15 UTC
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