Bug 2026860 - oauth-proxy should not break when the openshift-config-managed/oauth-serving-cert is unavailable
Summary: oauth-proxy should not break when the openshift-config-managed/oauth-serving-...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oauth-proxy
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Standa Laznicka
QA Contact:
Whiteboard: LifecycleReset
: 2062347 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2021-11-26 09:34 UTC by Standa Laznicka
Modified: 2023-04-21 07:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2023-01-16 14:43:05 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift oauth-proxy pull 238 0 None open Bug 2026860: ocp provider: don't fail client creation if oauth-server cert is not present 2022-01-06 10:20:58 UTC

Description Standa Laznicka 2021-11-26 09:34:30 UTC
Description of problem:
The oauth-proxy now expects the existence of the openshift-config-managed/oauth-serving-cert configMap. This may not be the case if a newer oauth-proxy version is used in an older cluster, leading to the oauth-proxy being broken.

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

How reproducible:

Steps to Reproduce:
1. try running a 4.9 oauth-proxy in front of your service in 4.8 cluster
2. attempt to log in to the oauth-proxy

Actual results:
500 internal error

Expected results:
login works

Additional info:

Comment 1 Michal Fojtik 2021-12-26 10:22:28 UTC
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Whiteboard if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.

Comment 2 Michal Fojtik 2022-01-19 18:11:47 UTC
The LifecycleStale keyword was removed because the bug moved to QE.
The bug assignee was notified.

Comment 8 Sergiusz Urbaniak 2022-03-24 10:36:25 UTC
*** Bug 2062347 has been marked as a duplicate of this bug. ***

Comment 11 Michal Fojtik 2023-01-16 14:43:05 UTC
Dear reporter, we greatly appreciate the bug you have reported here. Unfortunately, due to migration to a new issue-tracking system (https://issues.redhat.com/), we cannot continue triaging bugs reported in Bugzilla. Since this bug has been stale for multiple days, we, therefore, decided to close this bug.
If you think this is a mistake or this bug has a higher priority or severity as set today, please feel free to reopen this bug and tell us why. We are going to move every re-opened bug to https://issues.redhat.com. 

Thank you for your patience and understanding.

Note You need to log in before you can comment on or make changes to this bug.