Bug 2030961 - Customizing the OAuth server URL does not apply to upgraded cluster
Summary: Customizing the OAuth server URL does not apply to upgraded cluster
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oauth-apiserver
Version: 4.9
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.10.0
Assignee: Standa Laznicka
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks: 2037944
TreeView+ depends on / blocked
 
Reported: 2021-12-10 05:17 UTC by yheum
Modified: 2022-03-10 16:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:32:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-authentication-operator pull 528 0 None open Bug 2030961: endpoints checker: check only the custom hostname if configured 2022-01-03 12:37:20 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:33:08 UTC

Comment 2 Standa Laznicka 2022-01-03 08:57:38 UTC 
I'm missing:
- the status details of the ingress object
- must-gather link

If not provided within 7 days, I'm going to close this BZ.
Comment 8 Xingxing Xia 2022-01-18 05:23:58 UTC 
First tried to upgrade 4.8 env to 4.9 env, then customized the oauth route, but can't reproduce the issue.
The bug described that customized oauth route after upgraded 4.9 env met the issue. Based on my test, I believe solely customizing the oauth route after upgrade 4.9 can't reproduce it.
Comment 9 Xingxing Xia 2022-01-18 05:24:24 UTC 
Checked the must-gather, it shows that not only oauth route was customized but also the ingress.config domain and the openshift-ingress-operator/operator.openshift.io/ingresscontrollers/default.yaml ingress default cert were also customized. So, to reproduce it, it seems the reporter needs to clarify more background about what other things were done on the cluster.
Comment 16 errata-xmlrpc 2022-03-10 16:32:55 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
Note You need to log in before you can comment on or make changes to this bug.