@dwilson Any chance you can verify on 4.10? @jcaamano Any good way to verify this on a small scale cluster?
I don’t think so. This is strictly a scale bug and the problem won’t show at small sizes. Unless we are whiling to white box it and look into the logs or just limit the verification for regressions.
Verified on 4.10.23 1. installed 4.9.43 on AWS 2. scaled cluster up to 120 nodes 3. ran the node-density-ci-networkpolicy kube-burner workload for 2600 pods as described in https://bugzilla.redhat.com/show_bug.cgi?id=2089392#c2 4. upgraded to 4.10.23 which has the fix for this bz Upgrade successful in about 1 hr 45 min.
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 (Important: OpenShift Container Platform 4.10.24 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. https://access.redhat.com/errata/RHSA-2022:5664
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days