Created attachment 1702270 [details] image_count_graph Description of problem: On our 3.11 cluster used for CI we periodically prune images via a pod that looks like this: ``` containers: - args: - adm - prune - images - --certificate-authority=/var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt - --keep-tag-revisions=3 - --keep-younger-than=96h - --confirm=true command: - oc image: quay.io/openshift/origin-cli:4.5 imagePullPolicy: Always name: "" resources: limits: cpu: "2" memory: 8Gi requests: cpu: "1" memory: 4Gi serviceAccountName: image-pruner ``` The job always times out after four hours: https://prow.ci.openshift.org/job-history/gs/origin-ci-test/pr-logs/directory/rehearse-10177-periodic-ci-image-pruner Impact: This caused an outage of about 40 minutes today because the etcd went out of storage space. We worked around it by increasing the storage of etcd to 6gib from the default 4gib. This will only temporarily solve the problem as the number of images increases and once we are at 8gig we can not increase etcd storage further. This needs a fix until we hit that 8 gig limit or Openshift will not have CI anymore. Attached a graph of the rising image count. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The job successfully ran for five days, but made no progress, either. We MUST make changes to `oc adm prune` to make it run in parallel as needed or debugging this will be impossible.
No bug found during regression test on image pruner, so verify this bug now on $ oc version Client Version: 4.6.0-0.nightly-2020-09-29-170625 Server Version: 4.6.0-0.nightly-2020-09-29-170625 Kubernetes Version: v1.19.0+6ef2098
*** Bug 1885545 has been marked as a duplicate of this bug. ***
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