Bug 2030961

Summary: Customizing the OAuth server URL does not apply to upgraded cluster
Product: OpenShift Container Platform Reporter: yheum <yoeum>
Component: oauth-apiserverAssignee: Standa Laznicka <slaznick>
Status: CLOSED ERRATA QA Contact: Xingxing Xia <xxia>
Severity: high Docs Contact:
Priority: high    
Version: 4.9CC: aos-bugs, mfojtik, surbania
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:32:55 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: 2037944    

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