Bug 1753886 - Stop authentication operator stomping its own route
Summary: Stop authentication operator stomping its own route
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: apiserver-auth
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.2.0
Assignee: Standa Laznicka
QA Contact: scheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-20 07:20 UTC by Standa Laznicka
Modified: 2019-10-16 06:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:41:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-authentication-operator pull 200 0 None closed Bug 1753886: Don't stomp on our own route 2021-01-19 01:13:39 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:41:54 UTC

Description Standa Laznicka 2019-09-20 07:20:59 UTC
Description of problem:
authentication operator tries to update its own route on more or less each run of its sync loop.

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

How reproducible:
100%

Steps to Reproduce:
1. run cluster
2. watch authnentication-operator logs

Actual results:
"updating route" appears ever so often

Expected results:
authentication operator should only update the route when it changed so that its operator wouldn't be able to function.


Additional info:
caused by new default values in route fields .spec.to.weight and .spec.wildcardPolicy

Comment 3 errata-xmlrpc 2019-10-16 06:41:39 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-2019:2922


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