Description of problem: on Dashboard and through oc get co, you can see the openshift-samples operator upgrading roughly every 10 minutes or so. Version-Release number of selected component (if applicable): 4.4.5 How reproducible: Unknown Steps to Reproduce: 1. 2. 3. Actual results: NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE authentication 4.4.5 True False False 40d ... openshift-samples 4.4.5 True True False 6m17s ... Expected results: Stay as False in progressing until a cluster upgrade is ongoing? Additional info:
Created attachment 1694401 [details] cluster config cluster config
Created attachment 1694402 [details] operator log operator log
So yeah as I communicated with Jorgen in slack, this is a known bug, based on the debug data he was able to get me. I've marked this one as a duplicate of the known bug. As it turns out, the fix just went out today as part of 4.4.6....https://access.redhat.com/errata/RHBA-2020:2310 In addition to upgrading to that level, the customer can choose to stay at 4.4.5 now and employ one of the following workarounds: - if the customer does not care about samples, they can mark the samples operator as Removed, and the samples will be deleted from the cluster, and the clusteroperator status will stabilize. - if the customer wants the samples, then a cluster administrator can reset the samples operator by invoking oc delete configs.samples cluster this delete will clear out the state, and then the operator will re-create the samples and clusteroperator state as if this was the initial install of the cluster vs. the upgrade that was performed. And certainly stabilizing at 4.4.5 and then upgrading at the customer's choosing is of course OK as well. *** This bug has been marked as a duplicate of bug 1832344 ***