Bug 2011927

Summary: OLM should allow users to specify a proxy for GRPC connections
Product: OpenShift Container Platform Reporter: Alexander Greene <agreene>
Component: OLMAssignee: Alexander Greene <agreene>
OLM sub component: OLM QA Contact: kuiwang
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: kuiwang, tflannag
Version: 4.9   
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: OLM could not establish GRPC connections to CatalogSource pods that were only reachable through a proxy. Consequence: If a CatalogSource pod was behind a proxy, OLM could not connect to the proxy and the hosted operator content was unavailable for installation. Fix: Introduce a GRPC_PROXY environment variable that defines a proxy that OLM will utilize to establish connections to GRPC CatalogSources. Result: OLM can now be configured to use a proxy when connecting to GRPC CatalogSources.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:18:05 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:    
Bug Blocks: 2015799    

Description Alexander Greene 2021-10-07 18:45:29 UTC 
Description of problem:
OLM should allow users to specify a proxy for GRPC connectioins

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

How reproducible:
Always

Steps to Reproduce:
1. Create and deploy socks5 proxy
2. Update the OLM/Catalog Operator Deployments to specify the GRPC_PROXY environment variable and use the ip address of the proxy created in step 1

Actual results:
OLM fails to make the GRPC requests through the proxy

Expected results:
OLM makes the GRPC requests through the proxy

Additional info:
Comment 7 errata-xmlrpc 2022-03-10 16:18:05 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: OpenShift Container Platform 4.10.3 security 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-2022:0056