Bug 1932805 - e2e: test OAuth API connections in the tests by that name
Summary: e2e: test OAuth API connections in the tests by that name
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oauth-apiserver
Version: 4.8
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.8.0
Assignee: Lukasz Szaszkiewicz
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks: 1932806
TreeView+ depends on / blocked
 
Reported: 2021-02-25 10:08 UTC by Lukasz Szaszkiewicz
Modified: 2021-07-27 22:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1932806 (view as bug list)
Environment:
Last Closed: 2021-07-27 22:48:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 25879 0 None closed e2e: test OAuth API connections in the tests by that name 2021-02-25 10:10:14 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:48:51 UTC

Description Lukasz Szaszkiewicz 2021-02-25 10:08:49 UTC 
OAuth API connection reuse/creation tests defined at [1] were actually checking OpenShift API connections instead.


[1] https://github.com/stlaz/origin/blob/a86849c3c7890188558f77c1936c70bddde6e9e9/test/extended/util/disruption/controlplane/controlplane.go
Comment 1 Lukasz Szaszkiewicz 2021-02-25 10:12:30 UTC 
Since this was a fix for an e2e test there is nothing to be tested by the QE team. Please move it to VERIFY. Thanks.
Comment 5 errata-xmlrpc 2021-07-27 22:48:26 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.8.2 bug fix and 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-2021:2438
Note You need to log in before you can comment on or make changes to this bug.