Bug 1946994

Summary:	'migration-ui' pod does not inherit the 'no_proxy' setting from the migration operator
Product:	Migration Toolkit for Containers	Reporter:	Erik Nelson <ernelson>
Component:	UI	Assignee:	John Matthews <jmatthew>
Status:	CLOSED ERRATA	QA Contact:	Xin jiang <xjiang>
Severity:	unspecified	Docs Contact:	Avital Pinnick <apinnick>
Priority:	unspecified
Version:	1.4.2	CC:	ernelson, rjohnson
Target Milestone:	---
Target Release:	1.4.3
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:	2021-04-28 05:52:41 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 Erik Nelson 2021-04-07 13:01:16 UTC

Description of problem:

Migration-UI is not accesible when deployed in restricted network environment with cluster proxy set.
https_proxy, http_proxy and no_proxy envs are present in both operator and controller, however i didn't found no_proxy in migration-ui deployment envs.

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

How reproducible:
Every time

Steps to Reproduce:
1. Configure cluster no_proxy setting

Actual results:
Not present on the UI pod

Expected results:
Should be present on the UI pod

Additional info:
This has been fixed on master for 1.4.3.

https://github.com/konveyor/mig-operator/pull/615

Comment 4 Xin jiang 2021-04-14 08:03:57 UTC

verified with MTC 1.4.3. I can see https_proxy, http_proxy and no_proxy envs in migration-ui deployment envs

Comment 9 errata-xmlrpc 2021-04-28 05:52:41 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) tool image release advisory 1.4.3), 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:1439