Bug 1747366

Summary: [proxy] Error while validating cloud credentials in proxy-enabled upi/aws install
Product: OpenShift Container Platform Reporter: Gaoyun Pei <gpei>
Component: Cloud Credential OperatorAssignee: Joel Diaz <jdiaz>
Status: CLOSED ERRATA QA Contact: Gaoyun Pei <gpei>
Severity: high Docs Contact:
Priority: high    
Version: 4.2.0CC: ahoffer, jialiu, wzheng
Target Milestone: ---Keywords: TestBlocker
Target Release: 4.2.0   
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: 2019-10-16 06:39:13 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:

Comment 2 Devan Goodwin 2019-09-06 15:23:47 UTC
We'd been told we should always assume cloud APIs are reachable, but this does not seem to be working out, we're investigating adding proxy support, Joel Diaz is looking into this.

Comment 3 Stephen Cuppett 2019-09-09 14:05:35 UTC
*** Bug 1743483 has been marked as a duplicate of this bug. ***

Comment 4 Devan Goodwin 2019-09-09 14:28:08 UTC
Joel is working on this as we speak. We're going to do an initial phase hopefully today or tomorrow to allow proxy support. This initial step will not support *changing* the proxy env vars, you would need to manually delete the cred operator pods to do so.

Phase 2 will come hopefully by end of week, but there is some risk here, and will allow the cred minter to support changing the proxy vars.

Comment 7 Johnny Liu 2019-09-16 01:13:15 UTC
Verified this bug with 4.2.0-0.nightly-2019-09-12-114308 (privatelink + proxy), and PASS.

Comment 8 errata-xmlrpc 2019-10-16 06:39:13 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:2922