Bug 1878824

Summary:	Web console is not accessible when deployed on OpenShift cluster on IBM Cloud
Product:	Migration Toolkit for Containers	Reporter:	vaibhav <vpagar>
Component:	General	Assignee:	Ian <ibolton>
Status:	CLOSED ERRATA	QA Contact:	Xin jiang <xjiang>
Severity:	medium	Docs Contact:	Avital Pinnick <apinnick>
Priority:	high
Version:	1.3.0	CC:	arghosh, ernelson, jmatthew, rjohnson, sregidor
Target Milestone:	---
Target Release:	1.6.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1895964 (view as bug list)		Environment:
Last Closed:	2021-09-29 14:34:47 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:
Bug Depends On:	1895964
Bug Blocks:

Description vaibhav 2020-09-14 15:17:04 UTC

Description of problem:

Openshfit cluster is deployed on an IBM ROKS cluster ( IBM RedHat Openshift Kubernetes Service) where the authentication is managed externally by using IBM rocks SSO login, so there is no authentication operator available on the openshift cluster.

While installing the CAM operator on this cluster, we faced issues with the metadata info, I reported the bug for this issue #1857211, and we applied the workaround as per comment #4 on bug  https://bugzilla.redhat.com/show_bug.cgi?id=1857211 

Currently, we are facing issues while opening the CAM UI, as it tries to reach the OAuth server for authentication but as there is no authentication operator available on the cluster so it's failing, and UI is just showing a blank page without any error message. 

They have Grafana deployed on the same cluster, so for Grafana login there is a service account responsible to perform the authentication externally, (refer screenshots for more details), so customer want this to work in a similar way for the CAM tool as well.

Version-Release number of selected component (if applicable):

Openshift-4.5 
CAM- 1.2

How reproducible:

100% 

Steps to Reproduce:

Install CAM on an openshift cluster deployed on IBM ROKS cluster and try to open UI, (Not able to reproduce internally, as it needs IBM ROKS cluster)

Actual results:

CAM UI is not opening after accessing the CAM route. 

Expected results:

CAM UI should be accessible on the cluster. 

Additional info:

IBM ROKS cluster ( IBM RedHat Openshift Kubernetes Service ) will be solutions from IBM to the customers and customers will be migrating to IBM ROKs for many customers in future.  hence we request to provide priority in fixing the issues.

Comment 10 Erik Nelson 2020-10-05 12:04:49 UTC

https://github.com/konveyor/mig-ui/pull/967

Comment 25 Sergio 2021-09-14 16:06:16 UTC

Verified using MTC 1.6.0 and ROKS OCP 4.7
 openshift-migration-rhel8-operator@sha256:1b93e062d7f1d6242634f3f6f8306c1a13ae47212c7aa805e248b6fda8b43409
    - name: MIG_CONTROLLER_REPO
      value: openshift-migration-controller-rhel8@sha256
    - name: MIG_CONTROLLER_TAG
      value: 3b5efa9c8197fe0313a2ab7eb184d135ba9749c9a4f0d15a6abb11c0d18b9194
    - name: MIG_UI_REPO
      value: openshift-migration-ui-rhel8@sha256
    - name: MIG_UI_TAG
      value: ac56919a13dd6bbf36ce7a5dfc7696d3dfebe6c9438da64b3bcd1d70b33c549c


MTC UI can be accessed and used without any problem.


Moved to VERIFIED.

Comment 27 errata-xmlrpc 2021-09-29 14:34:47 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 (Moderate: Migration Toolkit for Containers (MTC) 1.6.0 security & bugfix update), 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-2021:3694