Description of problem:
SSIA, this is here just so that we don't forget
... also remove the "authentication.operator.openshift.io/managed" annotations from the user and oauth APIService objects
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 Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
The LifecycleStale keyword was removed because the bug moved to QE.
The bug assignee was notified.
Tested in 4.8.0-0.nightly-2021-02-19-111007 env:
$ oc get apiservice v1.oauth.openshift.io v1.user.openshift.io -o yaml | grep -A 2 " annotations:"
This indicates comment 1 annotation is removed. But CRD still has the field:
$ oc get crd authentications.operator.openshift.io -o yaml |grep -i ManagingOAuthAPIServer
description: ManagingOAuthAPIServer indicates whether this operator is managing OAuth related APIs...
Seems need bump.
I no longer see the field. I am not sure when this disappeared.
Verified in 4.8.0-0.nightly-2021-04-13-171608:
Running `oc get crd authentications.operator.openshift.io -o yaml`, no ManagingOAuthAPIServer field is defined now.
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.8.2 bug fix and 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.