Description of problem: The storage-client CronJob create too many jobs Version-Release number of selected component (if applicable): 4.14.0-160 How reproducible: always Steps to Reproduce: 1. deploy ocs client operator 2. scale down ocs client operator and edit cronjob so that it always goes to Pending state, like requiring huge resources Actual results: - all the pods generated from the job will stay in pending state and new jobs gets created without taking pending jobs into account Expected results: - if there's a job already created do not create new job at next tick Additional info: - targeted for 4.14.z - could be solved in fixed in many different ways, however the aim is not to hit pod limits when these jobs getting created concurrently every minute
I re-tested with full_version: 4.14.1-14. No unnecessary jobs were created, there was only one job in Pending state.
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: Red Hat OpenShift Data Foundation 4.15.0 security, enhancement, & bug fix 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-2024:1383