Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1813421

Summary:	CI tests do not use cluster provided proxy
Product:	OpenShift Container Platform	Reporter:	ewolinet
Component:	apiserver-auth	Assignee:	Maru Newby <mnewby>
Status:	CLOSED ERRATA	QA Contact:	pmali
Severity:	low	Docs Contact:
Priority:	low
Version:	4.5	CC:	aos-bugs, dhansen, mfojtik, nagrawal, scheng, skuznets, slaznick, xxia
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1813968 (view as bug list)		Environment:
Last Closed:	2020-07-13 17:20: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:	1813968

Comment 5 Standa Laznicka 2020-03-17 07:38:48 UTC

Note that the 2 failing tests don't prove that the tested component is broken, they prove that the tests are broken, one of them most probably can't be fixed as it tries to connect via HTTP/2-only connection, which does not seem to have proxying support in Go yet

Comment 6 Daneyon Hansen 2020-03-17 15:48:10 UTC

Standa,

Thanks for the note. If the tests are broken, do you know how to disable them?

Comment 7 Standa Laznicka 2020-05-20 10:21:37 UTC

The tests are not broken, there is a single test that just won't work in proxied environment as it currently seems technically undoable. I do not know how to disable a test based on which environment it runs in, unfortunately.

Comment 10 Standa Laznicka 2020-05-26 12:01:33 UTC

https://github.com/openshift/origin/pull/24700 should fix the auth-related e2e tests issues

Comment 13 Steve Kuznetsov 2020-06-04 15:23:36 UTC

Not sure why this got moved from apiserver/auth to infra. Moving back.

Comment 16 errata-xmlrpc 2020-07-13 17:20: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, 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-2020:2409