In https://github.com/openshift/cluster-policy-controller/pull/28 we've introduced a 5 minute delta which should be 8 hours. Make sure to update that before we ship 4.6.
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.
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, so we are closing this bug as WONTFIX. If you consider this bug still valuable, please reopen it or create new bug.
This has to happen, ideally before closing 4.6. Probably I'll do that within next week or two.
Checked with payload : 4.6.0-0.nightly-2020-09-08-123737, we could see logs like : [root@dhcp-140-138 ~]# oc logs -f po/kube-controller-manager-ip-10-0-178-138.us-east-2.compute.internal -c cluster-policy-controller |grep "Adding next periodic repair on" I0909 05:51:52.687059 1 namespace_scc_allocation_controller.go:244] Adding next periodic repair on 2020-09-09 13:51:52.687056532 +0000 UTC m=+28803.321270205 Will move to verified .
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.6 GA Images), 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-2020:4196