Description of problem: Builds for multiple kernel versions should be ran in parallel when possible Version-Release number of selected component (if applicable): master/release-4.11 How reproducible: While running SRO for hub/spoke, and having 3 spokes ( 2x4.10 , 1x4.9 ) I see random pattern on how the builds are scheduled. Sometimes the builds are sequential, sometimes the builds are in parallel. Example for builds running in parallel: # oc get all NAME READY STATUS RESTARTS AGE pod/acm-ice-4-18-0-305-40-2-el8-4-x86-64-1-build 1/1 Running 0 54s pod/acm-ice-4-18-0-305-45-1-el8-4-x86-64-1-build 1/1 Running 0 77s Example for builds running in sequential: # oc get all NAME READY STATUS RESTARTS AGE pod/acm-ice-4-18-0-305-40-2-el8-4-x86-64-1-build 0/1 Completed 0 98m pod/acm-ice-4-18-0-305-45-1-el8-4-x86-64-1-build 0/1 Completed 0 95m Steps to Reproduce: 1. run an SpecialResourceModule CR with multiple spokes with different versions 2. 3. Actual results: random way of running builds: parallel/sequential Expected results: consistent way the builds are ran, maybe managed by the quota/limits, for the case there are many pods that are running in parallel Additional info:
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.11.0 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:5069