Bug 1926110 - Unable to log in to MTC console deployed on a cluster configured with a proxy
Summary: Unable to log in to MTC console deployed on a cluster configured with a proxy
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: General
Version: 1.4.0
Hardware: Unspecified
OS: Unspecified
urgent
medium
Target Milestone: ---
: 1.4.2
Assignee: Ian
QA Contact: Xin jiang
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-08 09:17 UTC by Sergio
Modified: 2021-03-16 20:47 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-15 08:15:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github konveyor mig-ui pull 1123 0 None open Bug 1926110: proxy fix 2021-02-23 22:26:54 UTC
Red Hat Product Errata RHBA-2021:0814 0 None None None 2021-03-15 08:15:54 UTC

Description Sergio 2021-02-08 09:17:58 UTC 
Description of problem:
When we deploy MTC in a cluster using a proxy configuration (proxy object in 4.x), we cannot login to MTC using the UI.

Version-Release number of selected component (if applicable):
MTC 1.4.0
and MTC 1.3.2

How reproducible:
Always

Steps to Reproduce:
1. Deploy MTC in a 4.x cluster configured to use a proxy.

2. Login to MTC

Actual results:
We are redirected to the cluster's loggin screen, but after entering our credentials and clicking on "Log in" the screen times out and do not redirect us to the MTC application.

The callback times out https://migration-openshift-migration.apps.cam-tgt-15270.qe.devcluster.openshift.com/login/callback?code=....

Expected results:
We should not have any problem to log in.

Additional info:
MTC 1.2.5 can log in without problems.
Comment 4 Sergio 2021-03-08 14:20:51 UTC 
Still cannot login to the UI Web Console.

UI pods are not being deployed with the PROXY variables. 

It seems that we need to cherry pick this commit to 1.4.2 branch too https://github.com/konveyor/mig-operator/commit/61afcdb66a8c196a15e868cc6933101d94e3c49c

We move the BZ to ASSIGNED status again.
Comment 6 Sergio 2021-03-09 14:42:29 UTC 
We cannot login to the UI. We get a 502 Bad Gateway Error

We move the BZ to ASSIGNED status.
Comment 7 Sergio 2021-03-09 17:12:40 UTC 
Verified using MTC 1.4.2

openshift-migration-ui-rhel8@sha256:83f4b7bcc386e22163852b5a0468329c54f5881dcc7cfd041e8d153355652de7

The 502 Bad Gateway Error was due to the proxy failing because of the certificate. After configuring the squid proxy with "sslproxy_cert_error allow all" to skip this kind of failures we were able to login to the UI without problems.

We VERIFY this BZ, and we will create a new BZ in order to make sure that we add in the documentation a reference to this issue.
Comment 11 errata-xmlrpc 2021-03-15 08:15:36 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 (Migration Toolkit for Containers (MTC) image release advisory 1.4.2), 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-2021:0814
Note You need to log in before you can comment on or make changes to this bug.