Backport from https://bugzilla.redhat.com/show_bug.cgi?id=1854383
Description of problem:
The ingress operator fails to ensure a DNSRecord due to errors refreshing the token, restarting the operator fixes the issue.
Version-Release number of selected component (if applicable):
Start the Ingress Operator with a valid token.
Expire/Revoke that token manually or edit the secret to make it fail refreshing.
Operator should get in degraded status and DNSRecord should fail updating.
Steps to Reproduce:
Ingress operator move to degraded state, and start retrying the calls.
1) After n subsequent retries, ingress operator requests a new credential token from the cloud credential operator
2) Operator handlers an authentication error over other errors and request a new credential or restarts itself logging the error.
I will try to get as much information from the client as possible.
Restarting the operator
We'll look into doing the backport this upcoming sprint.
I’m adding UpcomingSprint, because I was occupied by fixing bugs with
higher priority/severity, developing new features with higher
priority, or developing new features to improve stability at a macro
level. I will revisit this bug next sprint.
The backport is merged but still needs to be verified.
verified with 4.5.0-0.nightly-2020-09-11-211229 and passed.
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 (OpenShift Container Platform 4.5.11 bug fix 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.