I'm setting a reminder for myself to update the aforementioned provider in 4.6. It was added in https://github.com/openshift/cluster-openshift-apiserver-operator/pull/347
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. If you have further information on the current state of the bug, please update it, otherwise this bug will be automatically closed in 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.
I'm setting a reminder for myself to update the aforementioned provider in the next sprint.
In 4.7 IsOAuthEncryptionConfigManagedByThisOperator must return true when encryption is off so that OAS-O doesn't manage the encryption config fo CAO.
moving to the next sprint.
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.
This bug hasn't had any activity 7 days after it was marked as LifecycleStale and both reporter and assignee were notified, so we are closing this bug as WONTFIX. If you consider this bug still valuable, please reopen it or create new bug.
The LifecycleStale keyword was removed because the bug got commented on recently. The bug assignee was notified.
I'm moving it to the next sprint as a reminder for myself to remove the controller in 4.7.
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.
Closing as it was updated in https://github.com/openshift/cluster-openshift-apiserver-operator/pull/416. Nothing to be validated by a QE.