Bug 1841080

Summary:	Short startingDeadlineSeconds might make pruner job not to trigger in time
Product:	OpenShift Container Platform	Reporter:	Ricardo Maraschini <rmarasch>
Component:	Image Registry	Assignee:	Ricardo Maraschini <rmarasch>
Status:	CLOSED ERRATA	QA Contact:	Wenjing Zheng <wzheng>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.5	CC:	aos-bugs
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:42:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ricardo Maraschini 2020-05-28 10:19:46 UTC

According to Kubernetes documentation[1] startingDeadlineSeconds "stands for the deadline in seconds for starting the job if it misses its scheduled time for any reason. After the deadline, the cron job does not start the job. Jobs that do not meet their deadline in this way count as failed jobs."

By default our prune job is being configured with this parameter set to 60 seconds, and according to discussions[2], due to performance constraints, the job may not be spawned in time.

We need to increase the default value to assure pruner job will run

[1] https://kubernetes.io/docs/tasks/job/automated-tasks-with-cron-jobs/
[2] https://coreos.slack.com/archives/CHY2E1BL4/p1590525101216400

Comment 3 Wenjing Zheng 2020-06-01 09:04:08 UTC

Verified on 4.5.0-0.nightly-2020-05-30-025738:
$ oc get cronjob image-pruner -o yaml | grep startingDeadlineSeconds
        f:startingDeadlineSeconds: {}
  startingDeadlineSeconds: 3600

Comment 4 errata-xmlrpc 2020-07-13 17:42:23 UTC

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, 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:2409