Bug 1671346

Summary:	Web console after upgrade to 3.9.60 shows different view.
Product:	OpenShift Container Platform	Reporter:	Vladislav Walek <vwalek>
Component:	Management Console	Assignee:	Robb Hamilton <rhamilto>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.9.0	CC:	aos-bugs, hasha, jokerman, mmccomas, spadgett
Target Milestone:	---	Keywords:	Reopened
Target Release:	3.9.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	None.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-20 08:46:58 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 Vladislav Walek 2019-01-31 13:10:00 UTC

Description of problem:

after upgrade from 3.9.40 to 3.9.60 the web console UI shows different tabs:

Before upgrade:
- From the top right corner to browse the catalog, we are redirected to:
https://<url>:8443/console/project/openshift-web-console/catalog

- When we click on Catalog (left corner), we are redirected to:
https://<url>:8443/console/project/openshift-web-console/catalog

After the upgrade:
- When we browse from the top right corner and click to deploy image or import yaml: (CHANGES, it seems like OpenShift 3.4)
https://<url>:8443/console/project/openshift-web-console/create?tab=deployImage
https://<url>:8443/console/project/openshift-web-console/create?tab=fromFile

- From the top right corner to browse the catalog, we are redirected to (CHANGES, it seems like OpenShift 3.4)
https://<url>:8443/console/project/openshift-web-console/create?tab=fromCatalog

The cluster has disable the service catalog with:
window.OPENSHIFT_CONSTANTS.DISABLE_SERVICE_CATALOG_LANDING_PAGE = true;

in disable-calatol.js script attached to the cm of the web console.

Version-Release number of selected component (if applicable):
OpenShift Container Platform 3.9.60

How reproducible:
disable the service catalog with:
window.OPENSHIFT_CONSTANTS.DISABLE_SERVICE_CATALOG_LANDING_PAGE = true;

deploy web console with 3.9.60.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Samuel Padgett 2019-01-31 15:56:48 UTC

This is expected. Setting `DISABLE_SERVICE_CATALOG_LANDING_PAGE` completely changes the console catalog experience. If you only want to disable the service catalog and not change the UI experience, you shouldn't set that extension property. You can disable service catalog in the Ansible inventory, and the console will fallback to using native templates instead of template service broker.

See https://docs.openshift.com/container-platform/3.9/install_config/install/advanced_install.html#enabling-service-catalog

Comment 6 Robb Hamilton 2019-02-01 18:57:41 UTC

PRs to resolve: 
* https://github.com/openshift/origin-web-console/pull/3112
* https://github.com/openshift/origin-web-console/pull/3113
* https://github.com/openshift/origin-web-console/pull/3114

Comment 8 shahan 2019-02-11 09:41:27 UTC

Click 'Add to project'->'Browser catalog' will navigate to the new experience when the disable the service catalog with:
window.OPENSHIFT_CONSTANTS.DISABLE_SERVICE_CATALOG_LANDING_PAGE = true;
v3.9
OpenShift Master: v3.9.69 
Kubernetes Master: v1.9.1+a0ce1bc657 
OpenShift Web Console: v3.9.69 

v3.10
OpenShift Master: v3.10.112
Kubernetes Master: v1.10.0+b81c8f8 
OpenShift Web Console: v3.10.112 

v3.11
OpenShift Master:v3.11.82 
Kubernetes Master: v1.11.0+d4cacc0 
OpenShift Web Console: v3.11.83 

Verified this bug.

Comment 9 shahan 2019-02-11 09:43:55 UTC

'Add to project'->'Deploy Image' and 'Add to project'->'Import YAML/JSON'  also navigate to the new experience.

Comment 11 errata-xmlrpc 2019-02-20 08:46:58 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/RHBA-2019:0331